What would really help with authoring high-performance workspaces, is to change a reader or writer into respectively a FeatureReader or FeatureWriter. This allows more versatility to switch from "dumb" (=traditional) reading and writing to "smart" reading and writing (more easily do actions after writing, or read in batches). This idea would lower the barrier for authors to transition to more advanced ways to read and write data.
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+13- Contributor
For context, its quite a lot of work to replace a fully configured reader (someone else might have built) into a FeatureReader, my personal best practice is to always start with a Creator->FeatureReader to be more flexible, if the Creator is still there after 10 iterations, I might switch it to a Reader. Same with Writers vs FeatureWriters which currently support concurrent writing, rather than be limited by one writer active at a time and not be able to extend actions after writing in a new iteration of a workspace (luckily Writers will have the option of concurrent writing in upcoming versions).
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.