On 4/18/19 4:51 PM, Erik Hatcher wrote:
> Jason - thanks for replying
>
> and I concur, it makes sense to open a JIRA for this.I'm glad there
> is an acceptable workaround, at least.
>
> I recall doing a fair bit of trial and error, asking 'nix folk and
> stackoverflow how to handle th
Jason - thanks for replying
and I concur, it makes sense to open a JIRA for this.I'm glad there is
an acceptable workaround, at least.
I recall doing a fair bit of trial and error, asking 'nix folk and
stackoverflow how to handle this stdin situation and honing in on what's there
now.
Hi Carsten,
I think this is probably worth a jira. I'm not familiar enough with
bin/post to say definitively whether the behavior you mention is a
bug, or whether it's "expected" in some odd sense. But there's enough
uncertainty that I think it's worth recording there.
Best,
Jason
On Fri, Apr
Hi all
I posted the question below some time back, concerning the unusual
behaviour of bin/post if there is no stdin.
There has been no comments to that, and maybe bin/post is quaint in that
regard - I ended up changing my application to POST directly on the Web
endpoint instead.
But I do have o
I'm working with a script where I want to send a command to delete all
elements in an index; notably,
/opt/solr/bin/post -c -d "*:*"
When run interactively, this works fine.
However, when run automatically as a cron job, it gives this interesting
output:
Unrecognized argument: "*:*"
If
I'm working with a script where I want to send a command to delete all
elements in an index; notably,
/opt/solr/bin/post -c -d "*:*"
When run interactively, this works fine.
However, when run automatically as a cron job, it gives this interesting
output:
Unrecognized argument: "*:*"
If
I'm working with a script where I want to send a command to delete all
elements in an index; notably,
/opt/solr/bin/post -c -d "*:*"
When run interactively, this works fine.
However, when run automatically as a cron job, it gives this interesting
output:
Unrecognized argument: "*:*"
If
