I'm writing this to get input on where we're going in the CLI domain with respect to organizational choices of our commands. Looking on 9x, I see bin/solr, bin/post, bin/postlogs scripts. Recently, most internal command plumbing has been centralized under bin/solr and thus you can do "bin/solr post" or "bin/solr postlogs" instead of "bin/post" and "bin/postlogs" respectively. Disclaimer: So I hear; I haven't tried them.
At this point, I think we have a choice: (A) Remove bin/post and bin/postlogs in 10. There's no question the code duplication should be eliminated but the question is really about the DX (developer user experience). Do we want one shell command, "bin/solr" to be all things Solr, not just Solr itself (starting Solr), but posting data to Solr (basically a Curl alternative)? It's already a kitchen sink of some miscellaneous things, granted. This annoys my organizational sensibilities. (B) Keep the scripts, but implement them as one-liners calling into "bin/solr post" or similar, and possibly not document on the bin/solr side that these commands are there as it's just for implementation convenience. After all, this was the actual motivation of the changes that have happened lately -- it's improving code maintenance/support. Good stuff; but do we need to change the DX on users too? Is this better for them? Separately, since there are so many commands in bin/solr that don't relate to starting Solr, maybe bin/solr-start should exist? (again, could be a one-liner call into one CLI backend for our convenience). This decision is a matter of taste; it's not really technical. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
