Do you have any exception? My gut feeling that it's an implementation
limitation.
On Mon, Nov 28, 2022 at 7:16 AM Chatree Srichart
wrote:
> Hello Mikhail,
>
> For the example nested documents:
>
> Example Indexing Syntax: Pseudo-Fields
>
> https://solr.apache.org/guide/8_11/indexing-nested-docum
On 11/27/22 18:03, Aravind Reddy Jangam wrote:
I created collection using below command, core name on each server is different
like doc1_shard1_replica_n15 & doc1_shard2_replica_n4
Is it possible to rename core name, I would like to have same core on all
servers like doc1
./bin/solr create_col
Have you looked at placement plug-in?Replica Placement Plugins :: Apache Solr Reference Guidesolr.apache.orgJan Høydahl28. nov. 2022 kl. 00:18 skrev Aravind Reddy Jangam :Thanks Shawn, Earlier I only started solr in cloud mode on serverI ran below command to create collection, after starting solr
Hi Mikhail,
Thank you for your response. I am currently using the script update processor,
but I have not been able to access the entire payload for processing.
cmd.solrDoc is not correctly reading the payload. I have a payload where it is
not recognizing a field value. This payload had four fi
Hello,
It's still not clear. Which update request params (or curl) you use? What
if you put content as a tiny string, and then complicate it step by step?
On Mon, Nov 28, 2022 at 7:27 PM Matthew Castrigno wrote:
> Hi Mikhail,
>
> Thank you for your response. I am currently using the script updat
Hello Mikhail,
I have to work with the payload as is, I cannot modify it. My entire solution
has a lot of other things going on which would just confuse the discussion.
The issue I am having can be recreated using the update handler with the script
enabled (as shown in the documentation example
Thanks
I tried creating rules to pin a specific shard to a specific server name like
below
But these rules didn’t take effect, can you specify how to specify rules to use
hostname
rule=shard:shard1,node_name:server1.com:8983_solr
rule=shard:shard2,node_name:server2.com:8983_solr
http://localhos
That is invalid JSON. The client needs to fix it. I’m surprised it indexes at
all. This should not be your problem.
Past that string into this: https://jsonlint.com
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Nov 28, 2022, at 12:57 PM, Matthew C
Hello Walter,
Thank you for your reply. Yes, it is invalid JSON. However, it is "my" problem
unfortunately.
I am looking for a way to filter the payload as a character string.
The charFilter would be great, however for that to work it would have to be
first recognized as a valid field.
Is the
I think the word “payload” is confusing me.
The client is sending a JSON document. That JSON document has a “content” field
which is string-valued and is escaped (stringified) JSON. Correct?
You want to parse that JSON and treat it as additional fields to index?
So this content (fragment):
"co
Thank you for your reply Walter. When I say "payload" I mean what you would put
in the raw data of a curl request. I am pretty sure SOLR would refer to this as
the "document"
To the question:
"You want to parse that JSON and treat it as additional fields to index?"
Yes, and it requires further
On 2022-11-28 4:59 PM, Matthew Castrigno wrote:
...
Once other side question is what are all these "& #8203" coming from and why
does solr put them in there?
Can you add to
https://issues.apache.org/jira/projects/SOLR/issues/SOLR-16469
I see them on logging tab and got nothing other than my
I have to edit the true content as URL defense is interfering. Hopefully this
will come through
curl --location --request GET '(edited) .sl1.stlukes-int. (edited)
:8983/solr/talix/index' \
--header 'Content-Type: application/json' \
--data-raw
'{"partner":"88027688-62c4-459a-b4d5-a8ecf9edd1bf",
I think I would write an update request processor script, take the value of the
“content” field, then parse that as JSON, then take those fields and add them.
https://solr.apache.org/guide/solr/latest/configuration-guide/script-update-processor.html
The update request processor scripts are a lit
On 2022-11-27 2:26 PM, dmitri maziuk wrote:
...
node 1:
Num Docs: 3275676
...
node 2:
Num Docs: 3112069
Found a sneaky little bug in the importer, now Solr reports 3,275,706
documents on each node.
The only remaining problem is my scripts claim to have POSTed 3,253,639
documents so now I
Hi, I know we can do something like below to update one row for one field in a
solr core:
curl http://host:port/solr/core_1/update?commit=true --data-binary $'[{"id" :
"1", "field1" : {"set":"test1"} }]'
I want to update all rows for one field with one value in a solr core. For
example, there
Hello Shushuai.
There's no 'columnar update' handler which you are asking for. It needs to
send per doc updates, but there's much sense in bulking them by sending
multiple update commands per request.
On Tue, Nov 29, 2022 at 6:27 AM Shushuai Zhu
wrote:
> Hi, I know we can do something like below
Hi Shushuai,
Like Mikhail said, bulking your updates will be way faster than sending
individual update requests. Depending on how large (or should I say small)
the actual value is you're setting, you might be able to send a few hundred
or even a few thousand updates per request.
If you're query
18 matches
Mail list logo