[ https://issues.apache.org/jira/browse/LUCENE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-1391: ---------------------------------- Affects Version/s: 2.9 3.0 This issue is still valid, ShingleMatrixFilter still sets its class name as type attribute for all tokens and resets flags to 0. Furthermore, ShingleMatrixFilter does not respect custom/new attributes at all (like KeywordAttribute). > Token type and flags values get lost when using ShingleMatrixFilter > ------------------------------------------------------------------- > > Key: LUCENE-1391 > URL: https://issues.apache.org/jira/browse/LUCENE-1391 > Project: Lucene - Java > Issue Type: Bug > Components: contrib/analyzers > Affects Versions: 2.4, 2.9, 3.0 > Reporter: Wouter Heijke > Assignee: Karl Wettin > Fix For: 3.1, 4.0 > > > While using the new ShingleMatrixFilter I noticed that a token's type and > flags get lost while using this filter. ShingleFilter does respect these > values like the other filters I know. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org