lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doron Cohen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-3596) DirectoryTaxonomyWriter extensions should be able to set internal index writer config attributes such as info stream
Date Sun, 27 Nov 2011 13:04:39 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Doron Cohen updated LUCENE-3596:
--------------------------------

    Attachment: LUCENE-3596.patch

Patch taking approach (1) above, and moving createIWC() to constructor. 

In addition fixed some javadoc comments, and added an assert to the constructor, which, only
when assertions are enabled, will verify that the IWC in effect is not an instance of TieredMergePolicy.
Imperfect as this is, it at least exposed the problem in current test (fixed to use newLogMP()).

I think this is ready to commit.
                
> DirectoryTaxonomyWriter extensions should be able to set internal index writer config
attributes such as info stream
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-3596
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3596
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/facet
>            Reporter: Doron Cohen
>            Assignee: Doron Cohen
>            Priority: Minor
>         Attachments: LUCENE-3596.patch, LUCENE-3596.patch
>
>
> Current protected openIndexWriter(Directory directory, OpenMode openMode) does not provide
access to the IWC it creates.
> So extensions must reimplement this method completely in order to set e.f. info stream
for the internal index writer.
> This came up in [user question: Taxonomy indexer debug |http://lucene.472066.n3.nabble.com/Taxonomy-indexer-debug-td3533341.html]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message