[
https://issues.apache.org/jira/browse/SOLR-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824775#comment-15824775
]
Noble Paul commented on SOLR-7268:
----------------------------------
you are right the {{-<param-name>=<param-value>}} can lead to conflicts we can
just have a generic param like {{-params key1=val1&key2=val2}} etc. Anyway ,
nobody has yet picked up the implementation
> Add a script to pipe data from other programs or files to Solr using SolrJ
> --------------------------------------------------------------------------
>
> Key: SOLR-7268
> URL: https://issues.apache.org/jira/browse/SOLR-7268
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools, SolrJ
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> I should be able to pipe JSON/XML/CSV or whatever is possible at the
> {{/update/*}} to a command which in turn uses SolrJ to send the docs to the
> correct leader in native format.
> In the following examples , all connection details of the cluster is put into
> a file called solrj.properties
> example :
> {noformat}
> #post a file
> cat myjson.json | bin/post -c gettingstarted -s http://localhost:8983/solr
> #or a producer program
> myprogram | bin/post -c gettingstarted -s http://localhost:8983/solr
> {noformat}
> The behavior of the script would be exactly similar to the behavior if I were
> to post the request directly to solr to the specified {{qt}} . Everything
> parameter the requesthandler accepts would be accepted as a
> {{-<param-name>=<param-value>}} format. The same things could be put into a
> properties file called {{indexer.properties}} and be passed as a -p
> parameter. The script would expect the following extra properties {{zk.url}}
> for cloud or {{solr.url}} for standalone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
