You need an extra step to install curl on Windows. I know it may seem esoteric but I bet there are still a fair share of folks who are on Windows.
D. On Wed, Apr 28, 2021 at 11:04 PM Ishan Chattopadhyaya < [email protected]> wrote: > We should remove the post tool > Altogether. Curl is good enough and recommended. > > On Thu, 29 Apr, 2021, 2:15 am Gus Heck, <[email protected]> wrote: > >> I've generally been of the impression/opinion that the Post Tool is >> really just a convenience for folks testing out solr to see what it can do, >> and not really meant as a production ingestion solution. >> >> A little while back I had a client that had a third party tool that >> "integrated with solr" by invoking post.jar on documents with a script to >> loop through all the files in a directory and post them (the third party >> software's direct example of how to integrate, not the client's idea at >> all). Needless to say this caused difficulties with the gigabytes of data >> the third party tool had stored in many directories. Of course I don't >> know, but I'd guess that someone with little experience was tasked with the >> integration with solr at the third party software company and they followed >> some examples... then turned them into an "integration" blissfully unaware >> of the limitations of what they had done. >> >> I just re-read the ref guide page on post tool >> <https://solr.apache.org/guide/8_8/post-tool.html>, and there's nothing >> there to indicate to the reader that this might not be a good production >> level solution. Also I notice a couple of recent Jira issues regarding >> handling of corner cases of strange (broken) behavior or content in a web >> site's response, giving the impression that that user (who reported both >> issues) might be treading a path that will stretch the bounds of what the >> post tool can/should be relied upon for. >> >> https://issues.apache.org/jira/browse/SOLR-15381 >> https://issues.apache.org/jira/browse/SOLR-15370 >> >> How do folks feel about adding a warning or info box at the top of post >> tool docs indicating that it is not meant as a production solution, only as >> a quick way to test out documents. We might also say something more >> concrete like "virtually any use for a corpus containing over a few >> thousand documents is a bad idea"? ... or something like that, suggestions >> welcome... >> >> If folks agree then it seems that these two issues are likely to be >> WONTFIX. >> >> -Gus >> >> -- >> http://www.needhamsoftware.com (work) >> http://www.the111shift.com (play) >> >
