Replies: 2 comments 1 reply
-
CLI was proposed in #7 though not with the use case you propose here. The thoughts for assisting folks who are afraid of java are several:
At the moment however a fully declarative config is not desirable because one sometimes wants to do things like probe for the number of processors on the machine and adjust the number of instances of the rate limiting step. (I have one very processor bound client, that actually does some of the work they need with C code that I helped them integrate into solr (and thus also the PreAnalyze processor). It's nice that I can test it locally and effectively utilize my 32 thread desktop, and then drop the same code onto a 96 vcpu machine and it just soaks up the extra capacity and starts using it. Having a DSL or declarative config becomes potentially more attractive after #173 is implemented, because that will cover the above case much more smoothly, but such things add maintenance weight and so far this has been a 1.1 man band operation, so I've kept it simple. |
Beta Was this translation helpful? Give feedback.
-
Contribitions, stories of attempts that failed. etc. welcome, of course (Also want to point out for readers that alt lang configuration is mentioned in the docs too... https://github.com/nsoft/jesterj/wiki/Plan-Providers#plans-in-other-jvm-based-languages Give it a shot, let me know how it goes. ;) |
Beta Was this translation helpful? Give feedback.
-
This framework seems capable, but I was surprised to find you need to compile Java to use it? Have you thought of making a CLI and a config file format to let users get started right away, and only power use cases would need to compile Java?
E.g.
Beta Was this translation helpful? Give feedback.
All reactions