gerlowskija commented on PR #2479:
URL: https://github.com/apache/solr/pull/2479#issuecomment-2145825393
A few high-level questions/concerns:
1. `bin/solr` already has an "api" tool, which can be used to invoke
streaming expressions e.g. `bin/solr api -get
"$SOLR_URL/techproducts/stream?expr=search(techproducts)"`. I'm all for
syntactic-sugar, but I wonder whether this is worth the maintenance cost if the
main thing that it "buys" us is saving people from having to provide the full
API path as the "api" tool requires?
2. If I'm reading the PR correctly, it looks like one other capability of
the proposed `bin/solr stream` tool is that it can evaluate streams "locally"
in some cases i.e. without a full running Solr. Which is pretty cool - you
could imagine a real super-user doing some pretty involved ETL that builds off
of an expression like: `update(techproducts, unique(cat(...)))`.
But I'd worry about some of the documentation challenges surrounding
this. For instance, how would a user know which expressions can be run
locally, and which require a Solr to execute on? For expressions that have a
mix of both locally and remotely-executed clauses, is there any way for a user
to know which clauses are executed where?
To clarify - I think the upside here is pretty cool, I'm just worried
about the documentation end and what we might need to make it usable by folks
in practice.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
