You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "John Diss (JIRA)" <ji...@apache.org> on 2013/12/13 00:43:07 UTC
[jira] [Updated] (LUCENENET-531) Incorrect parsing of when
resetting a prefix tree node ending in LEAF_BYTE
[ https://issues.apache.org/jira/browse/LUCENENET-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Diss updated LUCENENET-531:
--------------------------------
Attachment: lucene.net.contrib.spatial.node.patch
patches Lucene.Net.Spatial.Prefix.Tree.Node to handle LEAF_BYTE on tokens passed to Node.Reset()
> Incorrect parsing of when resetting a prefix tree node ending in LEAF_BYTE
> --------------------------------------------------------------------------
>
> Key: LUCENENET-531
> URL: https://issues.apache.org/jira/browse/LUCENENET-531
> Project: Lucene.Net
> Issue Type: Bug
> Components: Lucene.Net Contrib
> Affects Versions: Lucene.Net 3.0.3
> Environment: Lucene.Net.Contrib.Spatial
> Reporter: John Diss
> Priority: Critical
> Attachments: lucene.net.contrib.spatial.node.patch
>
>
> When a prefix tree node is constructed, there is an explicit check to test if the last char is LEAF_BYTE and its presence is handled appropriately. If the node is reused via the node.Reset method there is no such check which leads to issues if presented with a token ending in LEAF_BYTE. This manifests as "Unexpected char: +" in method QuadPrefixTree.QuadCell.MakeShape.
> I think this happens when building a cell from e.g a rectangle shape query parameter where the cell level is < grid depth.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)