I have figured out the problem. The schema was changed and index has been
deleted and rebuilt since then. But the index files might still contain the old
stale segments.
I replayed the situation by restoring the old data using 6.5, then do the
optimization, then upgrade the 6.6.1, and found ou
This error is not about DocValuesAsStored, but about
multiValued=true|false. It indicates that multiValued is set to
"false" for the current index but "true" in the new schema. At least
that's my guess
Best,
Erick
On Thu, Sep 21, 2017 at 11:56 AM, Xie, Sean wrote:
> Hi,
>
> When I upgrade th
thanks Shawn, that seems to be the error exactly.
On 02/29/2016 09:22 AM, Shawn Heisey wrote:
On 2/28/2016 3:31 PM, David Santamauro wrote:
I'm porting a 4.8 schema to 5.3 and I came across this new error when
I tried to group.field=f1:
unexpected docvalues type SORTED_SET for field 'f1' (ex
On 2/28/2016 3:31 PM, David Santamauro wrote:
>
> I'm porting a 4.8 schema to 5.3 and I came across this new error when
> I tried to group.field=f1:
>
> unexpected docvalues type SORTED_SET for field 'f1' (expected=SORTED).
> Use UninvertingReader or index with docvalues.
>
> f1 is defined as
>
>
On 02/29/2016 07:59 AM, Tom Evans wrote:
On Mon, Feb 29, 2016 at 11:43 AM, David Santamauro
wrote:
You will have noticed below, the field definition does not contain
multiValues=true
What version of the schema are you using? In pre 1.1 schemas,
multiValued="true" is the default if it is omi
On Mon, Feb 29, 2016 at 11:43 AM, David Santamauro
wrote:
> You will have noticed below, the field definition does not contain
> multiValues=true
What version of the schema are you using? In pre 1.1 schemas,
multiValued="true" is the default if it is omitted.
Cheers
Tom
On 02/29/2016 06:05 AM, Mikhail Khludnev wrote:
On Mon, Feb 29, 2016 at 12:43 PM, David Santamauro <
david.santama...@gmail.com> wrote:
unexpected docvalues type SORTED_SET for field 'f1' (expected=SORTED). Use
UninvertingReader or index with docvalues.
DocValues is primary citizen api f
On Mon, Feb 29, 2016 at 12:43 PM, David Santamauro <
david.santama...@gmail.com> wrote:
>
> So I started over (deleted all documents), re-deployed configs to
> zookeeper and reloaded the collection.
>
> This error still appears when I group.field=f1
>
> unexpected docvalues type SORTED_SET for fie
So I started over (deleted all documents), re-deployed configs to
zookeeper and reloaded the collection.
This error still appears when I group.field=f1
unexpected docvalues type SORTED_SET for field 'f1' (expected=SORTED).
Use UninvertingReader or index with docvalues.
What exactly does th
David, this is tad weird. I've seen this error if you turn on docvalues for
an existing field. You can running an "optimize" on your index and see if it
helps.
--
View this message in context:
http://lucene.472066.n3.nabble.com/docValues-error-tp4260408p4260455.html
Sent from the Solr - User ma
Ugh! I totally missed the highlight.
Thanks for clarifying.
On 11/13/15, 1:07 PM, "Anshum Gupta" wrote:
>Hi Devansh,
>
>Yes you'd need to reindex your data in order to use DocValues. It's
>highlighted here @ the official ref guide :
>
>https://cwiki.apache.org/confluence/display/solr/DocVa
Hi Devansh,
Yes you'd need to reindex your data in order to use DocValues. It's
highlighted here @ the official ref guide :
https://cwiki.apache.org/confluence/display/solr/DocValues
On Fri, Nov 13, 2015 at 10:00 AM, Dhutia, Devansh
wrote:
> We have an existing collection with a field called l
12 matches
Mail list logo
