an the update script
> It produced reams of data but not errors. just a bunch of DEBUG lines
> would you like me to post it?
>
> K
>
> - Original Message -
>
> From: "Erick Erickson"
> To: "solr-user"
> Sent: Friday, December 23, 2016 1:22:37 P
2:37 PM
Subject: Re: update operation
OK, next thing. Find your Solr log and tail -f on it while you send
you doc. That answers what Solr actually sees .vs. what you think
you're sending it ;). If anything.
Best,
Erick
On Fri, Dec 23, 2016 at 10:15 AM, KRIS MUSSHORN wrote:
>
OK, next thing. Find your Solr log and tail -f on it while you send
you doc. That answers what Solr actually sees .vs. what you think
you're sending it ;). If anything.
Best,
Erick
On Fri, Dec 23, 2016 at 10:15 AM, KRIS MUSSHORN wrote:
> oops wrong thread in subject
>
> - Original Messag
oops wrong thread in subject
- Original Message -
From: "KRIS MUSSHORN"
To: solr-user@lucene.apache.org
Sent: Friday, December 23, 2016 1:02:09 PM
Subject: Re: copying all fields to one specific single value field
Well i guess its still not working..
I'm not getting an error but i
citly commit?
>> Sorry for the silly questions but im pretty fried
>>
>> - Original Message -
>>
>> From: "Erick Erickson"
>> To: "solr-user"
>> Sent: Thursday, December 22, 2016 2:49:05 PM
>> Subject: Re: update operation
>>
&
ursday, December 22, 2016 2:49:05 PM
> Subject: Re: update operation
>
> Kris:
>
> Maybe too simple, but did you commit afterwards?
>
> On Thu, Dec 22, 2016 at 10:45 AM, Shawn Heisey wrote:
>> On 12/22/2016 10:18 AM, KRIS MUSSHORN wrote:
>>> UPDATE_RESULT=$( curl -s -
How would i exp;licitly commit?
Sorry for the silly questions but im pretty fried
- Original Message -
From: "Erick Erickson"
To: "solr-user"
Sent: Thursday, December 22, 2016 2:49:05 PM
Subject: Re: update operation
Kris:
Maybe too simple, but did you com
Kris:
Maybe too simple, but did you commit afterwards?
On Thu, Dec 22, 2016 at 10:45 AM, Shawn Heisey wrote:
> On 12/22/2016 10:18 AM, KRIS MUSSHORN wrote:
>> UPDATE_RESULT=$( curl -s -X POST -H 'Content-Type: text/json'
>> "https://snip/solr/TEST_CORE/update/json/docs"; --data-binary
>> '{"id
On 12/22/2016 10:18 AM, KRIS MUSSHORN wrote:
> UPDATE_RESULT=$( curl -s -X POST -H 'Content-Type: text/json'
> "https://snip/solr/TEST_CORE/update/json/docs"; --data-binary
> '{"id":"*'$DOC_ID'","metatag.date.single":{"set":"$VAL"}}')
>
> was the only version that did not throw an error but did
was the only version that did not throw an error but did not update the
document.
It returned:
{"responseHeader":{"status":0,"QTime":1}}
Where do i go from here?
K
- Original Message -----
From: "Shawn Heisey"
To: solr-user@luce
Shawn,
Perhaps i misunderstood the documentation but when you included the add clause
does it not create an entirely new document?
K
- Original Message -
From: "Shawn Heisey"
To: solr-user@lucene.apache.org
Sent: Thursday, December 22, 2016 11:00:21 AM
Subject:
On 12/22/2016 8:45 AM, KRIS MUSSHORN wrote:
> Here is the bash line:
>
> UPDATE_RESULT=$( curl -s "https://snip/solr/TEST_CORE/update?&commit=true";
> --data-binary '{"id":"$DOC_ID","metatag.date.single" :{"set":"$VAL"}}')
One thing I know you need for sure with the "/update" handler is the
Con
12 matches
Mail list logo
