Just a casual comment..
This issue marks another big milestone in  solr/lucene evolution, it
moves into new direction of being not only search library, but rather
full data storage/manipulation solution. Who needs sql and nosql db-s,
they cannot search without painful integration :)

Imo, this issue is symbolically just as important for us users as flex
indexing was.

Flex Indexing and column stride fields are great infrastructure to
build upon, but they also started with one small step by making
omitTf hack :) Mike is great with his "progress, not perfection"

cheers, eks



On Sun, Aug 7, 2011 at 7:44 PM, Yonik Seeley (JIRA) <j...@apache.org> wrote:
>
>     [ 
> https://issues.apache.org/jira/browse/SOLR-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
>
> Yonik Seeley updated SOLR-2700:
> -------------------------------
>
>    Attachment: SOLR-2700.patch
>
> Here's an update that handles delete-by-id and also makes lookups concurrent 
> (no synchronization on the file reads so multiple can proceed at once).
>
>> transaction logging
>> -------------------
>>
>>                 Key: SOLR-2700
>>                 URL: https://issues.apache.org/jira/browse/SOLR-2700
>>             Project: Solr
>>          Issue Type: New Feature
>>            Reporter: Yonik Seeley
>>         Attachments: SOLR-2700.patch, SOLR-2700.patch
>>
>>
>> A transaction log is needed for durability of updates, for a more performant 
>> realtime-get, and for replaying updates to recovering peers.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to