Thanks Vincenzo! I will check the schema too.
On 2022/06/07 16:08:21 Vincenzo D'Amore wrote:
> The easiest thing to do is double check your schema.xml and see how the
> field type "string" is defined.
>
> On Tue, Jun 7, 2022 at 3:44 PM Poorna Murali wrote:
>
> > If docValues are enabled by defaul
Thanks Thomas! I will check the same.
On 2022/06/07 19:01:37 Thomas Corthals wrote:
> You can ask Luke:
> http://localhost:8983/solr/techproducts/admin/luke?show=all&fl=id
>
> On Solr 8.11.1, I get this snippet as part of the output:
>
> "fields":{
> "id":{
> "type":"string",
> "
You can ask Luke:
http://localhost:8983/solr/techproducts/admin/luke?show=all&fl=id
On Solr 8.11.1, I get this snippet as part of the output:
"fields":{
"id":{
"type":"string",
"schema":"I-S-U-OF-l",
If it had docValues="true" in the schema, the fourth flag would be a D
Thanks Gus! The only way to check if docValues is enabled for a field is by
ensuring that the field cache is not getting populated while we do a sort
on that field. Please confirm if my understanding is correct.
On 2022/06/07 15:27:23 Gus Heck wrote:
> Sorry, was thinking this was about doc values
The easiest thing to do is double check your schema.xml and see how the
field type "string" is defined.
On Tue, Jun 7, 2022 at 3:44 PM Poorna Murali wrote:
> If docValues are enabled by default for string field, then the sort queries
> on the field will not occupy field cache and would rather re
Commenting out the stop filter allowed documents to be indexed, confirming
it was actually the problem. But then queries fail because of not being
able to find the synonyms for what looks like a similar reason.
I've also tried switching the files to use absolute paths like below, but
that also doe
Sorry, was thinking this was about doc values as stored... but re-reading
that might not be the case (a mail client adding RE: is messing up the
threading here)... Another common problem is if you are using old schemas
from old versions, some of the "by default" stuff is based on the default
schema
check your schema version attribute
https://github.com/apache/solr/blob/main/solr/server/solr/configsets/_default/conf/managed-schema.xml#L41
On Tue, Jun 7, 2022 at 9:43 AM Poorna Murali wrote:
> If docValues are enabled by default for string field, then the sort queries
> on the field will not
I had an 8.11.1 implementation in progress when 9.0 came out, and am trying
to convert it so we don't go live on an already outdated version. I'm
having trouble adding documents to the index that worked fine with 8.11.1.
Shortened error is below:
2022-06-07 13:49:24.190 ERROR (qtp554868511-21) [ x
If docValues are enabled by default for string field, then the sort queries
on the field will not occupy field cache and would rather rely on
docValues. But in our case, it is filling up the field cache and that is
the reason we are planning to enable docValues for that field.
Is this functionalit
"string" field type usually has "docValues"=true as default.
On Tue, Jun 7, 2022 at 11:22 AM Poorna Murali
wrote:
> Hi All,
>
> We have an id field(unique key) in our schema as follows,
> multiValued=“false”/>
>
> We are planning to introduce docValues to this field to save fieldcache
> space.
Hi All,
We have an id field(unique key) in our schema as follows,
We are planning to introduce docValues to this field to save fieldcache
space. My understanding on this is that, going forward all the sort or
faceting done on id field will make use of docValues and since the stored
flag is true
Hi,
I want to use the update processor of solr, on nested doc.
for example this is the nested doc:
{
"id":3
"texts":[
{
"id":2
"tmp":["dsa", "dsa", "ewq"]
}
]
}
and I want to use the UP - UniqFieldsUpdateProcessor on the texts.tmp field.
how can I do this?
13 matches
Mail list logo
