Updating documents with docvalues (not stored), commit question

[Dorian Hoxha <do...@gmail.com>]

Looks like you can update documents even using just doc-values (without
stored). While I understand the columnar-format, my issue with this is that
docValues are added when a 'commit' is done (right?). Does that mean that
it will force a commit (which is a slow operation) when updating with
docValues or does it do something more smart ?

Thank You

Re: Updating documents with docvalues (not stored), commit question

[Erick Erickson <er...@gmail.com>]

I'm pretty sure that atomic updates use Real Time Get which means they'll
pull the values from in-memory structures for docs that haven't been
committed yet.

And as Shawn says, docValues isn't relevant here.

Best,
Erick

On Thu, Nov 17, 2016 at 5:52 AM, Shawn Heisey <ap...@elyograg.org> wrote:
> On 11/17/2016 6:26 AM, Dorian Hoxha wrote:
>> Looks like you can update documents even using just doc-values
>> (without stored). While I understand the columnar-format, my issue
>> with this is that docValues are added when a 'commit' is done
>> (right?). Does that mean that it will force a commit (which is a slow
>> operation) when updating with docValues or does it do something more
>> smart ?
>
> The presence  or absence of docValues does not change commits at all.  A
> commit is a separate operation from indexing, although you can send
> commit=true with an indexing request and it would be started as soon as
> all the indexing for that request is done.
>
> https://lucidworks.com/blog/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
>
> The URL above says "SolrCloud" but what it says also applies to
> non-cloud installs.
>
> Thanks,
> Shawn
>

Re: Updating documents with docvalues (not stored), commit question

[Shawn Heisey <ap...@elyograg.org>]

On 11/17/2016 6:26 AM, Dorian Hoxha wrote:
> Looks like you can update documents even using just doc-values
> (without stored). While I understand the columnar-format, my issue
> with this is that docValues are added when a 'commit' is done
> (right?). Does that mean that it will force a commit (which is a slow
> operation) when updating with docValues or does it do something more
> smart ? 

The presence  or absence of docValues does not change commits at all.  A
commit is a separate operation from indexing, although you can send
commit=true with an indexing request and it would be started as soon as
all the indexing for that request is done.

https://lucidworks.com/blog/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/

The URL above says "SolrCloud" but what it says also applies to
non-cloud installs.

Thanks,
Shawn