The post tool should be removed completely.

On Wed, 17 May, 2023, 7:06 pm Gus Heck, <gus.h...@gmail.com> wrote:

> I suspect we could do without the webcrawl one too. Honestly these should
> only be considered for demonstration or extremely small installations, and
> anything not used in the tutorials could be cut IMHO.
>
> On Wed, May 17, 2023 at 7:32 AM Eric Pugh <ep...@opensourceconnections.com
> >
> wrote:
>
> > Hi all,
> >
> > As part of SOLR-6994 I’m migrating the SimplePostTool to be part of
> > bin/solr commands.
> >
> >
> > We document a number of example use cases:
> >
> > * JSON file: bin/solr post -url http://localhost:8983/wizbang/update
> > events.json
> > * XML files: bin/solr post -url http://localhost:8983/records/update
> > article*.xml
> > * CSV file: bin/solr post -url http://localhost:8983/signals/update
> > LATEST-signals.csv
> > * Directory of files: bin/solr post -url
> > http://localhost:8983/myfiles/update ~/Documents
> > * Web crawl: bin/solr post -url
> > http://localhost:8983/gettingstarted/update https://solr.apache.org/
> > -recursive 1 -delay 1
> > * Standard input (stdin): echo '{commit: {}}' | bin/solr post -url
> > http://localhost:8983/my_collection/update -type application/json -out
> > yes -d
> > * Data as string: bin/solr post -url
> http://localhost:8983/signals/update
> > -type text/csv -out yes -d $'id,value\n1,0.47'
> >
> >
> > The last two, stdin and data as a string,  feel rather obscure to me, and
> > I’d like to not port them over to being supported by the bin/solr post
> tool
> > equivalent.    Thoughts?
> >
> > Eric
> > _______________________
> > Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 |
> > http://www.opensourceconnections.com <
> > http://www.opensourceconnections.com/> | My Free/Busy <
> > http://tinyurl.com/eric-cal>
> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <
> >
> https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw
> >
> >
> > This e-mail and all contents, including attachments, is considered to be
> > Company Confidential unless explicitly stated otherwise, regardless of
> > whether attachments are marked as such.
> >
> >
>
> --
> http://www.needhamsoftware.com (work)
> http://www.the111shift.com (play)
>

Reply via email to