[
https://issues.apache.org/jira/browse/SOLR-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-7268:
-----------------------------
Description:
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/solr index -qt=/update/json/docs -p indexer.properties
#or a producer program
myprogram | bin/solr index -qt=/update/json -p indexer.properties
{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.
was:
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 | solr/bin/indexer -qt=/update/json/docs -p
indexer.properties
#or a producer program
myprogram | solr/bin/indexer -qt=/update/json -p indexer.properties
{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.
> 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
> 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/solr index -qt=/update/json/docs -p indexer.properties
> #or a producer program
> myprogram | bin/solr index -qt=/update/json -p indexer.properties
> {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]
