lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <>
Subject [jira] [Commented] (SOLR-4085) Commit-free ExternalFileField
Date Mon, 03 Dec 2012 19:39:59 GMT


Mikhail Khludnev commented on SOLR-4085:

[~rcmuir], I don't think this feature can be a fix for "bugs, saying X or Y doesn't work"
it's about adding new ability. eg until updateable DocValues are delivered it's hardly possible
to raise a bug "can't update docvalues", because it will be rejected 'by design'. Or I completely
I misunderstood you.

[] aha. thanks. Initially I had a test enforces atomicity, achieve it for
QParsers via SolrQueryRequest.context, but failed to provide it for query cache warming. I'm
not so self-assured to introduce treadlocal, but now it's clear how to do that. 

[~jpountz] [~romseygeek] pls consider my point: Solr doesn't protect if somebody want to shoot
his leg off. let's we have fairly valid updateXml: 
{code}delQ *:* add-doc(1), add-doc(2),add-doc(3), commit {code} you can send this sequence
*twice* in different requests - everything will be ok. But if these requests overlaps in time,
you've got "an unpleasant behavior" user will see some intermediate state. If I got it right
and Solr doesn't protect from externally initiated race (only DIH somehow does it), should
we care about "intermediate state" and wasteful reloads in EFF.

Colleagues, please articulate your expectation for concurrent reload, and if I'd be able to
conquer with them I handle "atomicity" also. 

> Commit-free ExternalFileField
> -----------------------------
>                 Key: SOLR-4085
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: Schema and Analysis
>    Affects Versions: 4.1
>            Reporter: Mikhail Khludnev
>              Labels: externalfilefield
>         Attachments: SOLR-4085.patch
> Let's reload ExternalFileFields without commit!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message