[
https://jira.nuxeo.org/browse/NXP-6197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stéphane Lacoin updated NXP-6197:
---------------------------------
Description:
In some cases where successive transactions are performed very fast, some
document copies can get the wrong fulltext information.
Example :
1) the user creates a new document (first transaction)
2) the user copies the document (second transaction)
3) the binary listener performs the indexation (third transaction) (consequence
of the first, but asynchronous)
As the full-text row is copied before the information was available, the copy
is referencing the wrong full-text information until the document binaries will
be re-indexed.
One way of solving is to mark the document with the indexing job id in the
session that was altering the document. This way, once the indexing completes,
all documents that references this indexing job id will be updated with the
computed full-text information.
Impacts are:
* org.nuxeo.ecm.core.storage.sql.SessionImpl.updateFulltext()
*
org.nuxeo.ecm.core.storage.sql.coremodel.BinaryTextListener.handleEvent(EventBundle)
was:
In some cases where successive transactions are performed very fast, some
document copies can get the wrong fulltext information.
Example :
1) the user creates a new document (first transaction)
2) the user copies the document (second transaction)
3) the binary listener performs the indexation (third transaction) (consequence
of the first, but asynchronous)
As the full-text row is copied before the information was available, the copy
is referencing the wrong full-text information until the document binaries will
be re-indexed.
We have the same problem with the check-in operation that makes a deep copies
of the VCS data structure.
One way of solving is to mark the document with the indexing job id in the
session that was altering the document. This way, once the indexing completes,
all documents that references this indexing job id will be updated with the
computed full-text information.
Impacts are:
* org.nuxeo.ecm.core.storage.sql.SessionImpl.updateFulltext()
*
org.nuxeo.ecm.core.storage.sql.coremodel.BinaryTextListener.handleEvent(EventBundle)
Remaining Estimate: 0 minutes
Original Estimate: 0 minutes
> Ensure fulltext is correct after checkin (versioning) or copy
> -------------------------------------------------------------
>
> Key: NXP-6197
> URL: https://jira.nuxeo.org/browse/NXP-6197
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Core SQL Storage
> Affects Versions: 5.4
> Reporter: Stéphane Lacoin
> Assignee: Stéphane Lacoin
> Priority: Major
> Fix For: 5.4.1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> In some cases where successive transactions are performed very fast, some
> document copies can get the wrong fulltext information.
> Example :
> 1) the user creates a new document (first transaction)
> 2) the user copies the document (second transaction)
> 3) the binary listener performs the indexation (third transaction)
> (consequence of the first, but asynchronous)
> As the full-text row is copied before the information was available, the copy
> is referencing the wrong full-text information until the document binaries
> will be re-indexed.
> One way of solving is to mark the document with the indexing job id in the
> session that was altering the document. This way, once the indexing
> completes, all documents that references this indexing job id will be updated
> with the computed full-text information.
> Impacts are:
> * org.nuxeo.ecm.core.storage.sql.SessionImpl.updateFulltext()
> *
> org.nuxeo.ecm.core.storage.sql.coremodel.BinaryTextListener.handleEvent(EventBundle)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
