[ 
https://issues.apache.org/jira/browse/LUCENE-4590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511262#comment-13511262
 ] 

Doron Cohen commented on LUCENE-4590:
-------------------------------------

bq. Do you think perhaps that EnwikiContentSource should let the caller know 
whether the returned DocData represents a content page or category page?

That's what I planned at start, but decided to leave WriteLineDoc intact 
because it is general, that is, not aware of the unique structure of Wikipedia 
data, where some of the pages represent categories.

bq. So maybe, if someone wants to generate a line file from the pages only... 
flexibility that I think you are trying to achieve...

Actually I am after the two files... :) These category pages are (unique) 
taxonomy node names, but without the taxonomy structure, which can be deduced 
from the (parent) categories of the category pages. Having this separate 
category pages can be useful for deducing that taxonomy.
                
> WriteEnwikiLineDoc which writes Wikipedia category pages to a separate file
> ---------------------------------------------------------------------------
>
>                 Key: LUCENE-4590
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4590
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/benchmark
>            Reporter: Doron Cohen
>            Assignee: Doron Cohen
>            Priority: Minor
>
> It may be convenient to split Wikipedia's line file into two separate files: 
> category-pages and non-category ones. 
> It is possible to split the original line file with grep or such.
> It is more efficient to do it in advance.

--
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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to