stroomdev66
stroomdev66
It should be possible to choose which nodes process which data by making processor filters target node groups (gh-1623).
All Stroom content could be stored in Git and versioned accordingly. Multiple Git repositories could be connected to provide some read only content provided as standard or by other parties...
It would be helpful for you to be able to find certain Stroom content, e.g. XSLT, with a free text search as it is often quite hard to remember which...
We need some better answers to shared storage other than just NFS especially when some customers only have access to local disk or SAN. Possible solutions might include the use...
At the moment it is easy to break the system by deleting content that is used by another piece of content, e.g. an XSLT being used by a pipeline. Stroom...
This would be a big change to the way data is processed, switching from batches of events (aka streams) to single events. It may allow for more even scaling of...
It would be good if the properties specified an alias that could be used in the include to ensure uniqueness of the import. The pipeline properties system would need enhancing...
It would be useful if some processor filters were only used by certain nodes so that specific nodes performed specific processing tasks, e.g. index creation.
This is useful when using reference data that is known to arrive late