You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/01/20 16:31:43 UTC
[jira] Created: (OODT-117) Final File Location Extractor fails in
actual use despite unit test passing
Final File Location Extractor fails in actual use despite unit test passing
---------------------------------------------------------------------------
Key: OODT-117
URL: https://issues.apache.org/jira/browse/OODT-117
Project: OODT
Issue Type: Bug
Components: file manager
Environment: Cent OS fresh install, JDK 1.6, Maven 2.2.1, Tomcat 5.5.31
Reporter: Chris A. Mattmann
Assignee: Chris A. Mattmann
Priority: Blocker
Fix For: 0.2
The File Manager's FinalFileLocationExtractor contributed in OODT-72 fails in practice, performing some operation out of order causing the LuceneCatalog to barf out error messages saying the product isn't unique in the catalog. This is despite the unit test I contributed passing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OODT-117) Final File Location Extractor fails in
actual use despite unit test passing
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann resolved OODT-117.
------------------------------------
Resolution: Fixed
- fixed in r1062100. This was a tricky, interesting one. The LuceneCatalog tries to guess when refs + met have been added for the cached product before committing it to Lucene. Since the FinalFileLocationExtractor ran the versioner, the data store refs on the server side were set forcing the auto flush/commit of the product to lucene. Then on the client side, when addProductReferences was called, the product had already been flushed to Lucene and wasn't part of the cache, causing an error.
It's fixed now by modding the FinalFileLocationExtractor to scrub the dataStore portions of each prod ref back to "", and I also updated the unit test to test for this too.
> Final File Location Extractor fails in actual use despite unit test passing
> ---------------------------------------------------------------------------
>
> Key: OODT-117
> URL: https://issues.apache.org/jira/browse/OODT-117
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Environment: Cent OS fresh install, JDK 1.6, Maven 2.2.1, Tomcat 5.5.31
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Priority: Blocker
> Fix For: 0.2
>
>
> The File Manager's FinalFileLocationExtractor contributed in OODT-72 fails in practice, performing some operation out of order causing the LuceneCatalog to barf out error messages saying the product isn't unique in the catalog. This is despite the unit test I contributed passing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.