[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-416) Analyze Payload and how this could be used to store id and class in the index and not the document

[Sanne Grinovero (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35372#action_35372 ] 

Sanne Grinovero commented on HSEARCH-416:
-----------------------------------------

I need to try some benchmarks to fully understand it, but think the idea is to add the payload only to the @DocumentId term, so the term value could be optionally empty if the user doesn't need to search by PK in Lucene, but store the link to database PK as payload.
Being the payload a byte[] you should add a new interface similar to current TwoWayStringBridge to care for optimal conversion from (and to) all key types.

The optimal case assumes to be able to convert the keys into integers, so that they can be used as index in an array, not sure if it's still efficient to support other types which would require a Map as cache. In this case we could support this only when the key is of type Integer, which saves you from the new bridging interface.

> Analyze Payload and how this could be used to store id and class in the index and not the document
> --------------------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-416
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-416
>             Project: Hibernate Search
>          Issue Type: Sub-task
>          Components: engine
>            Reporter: Emmanuel Bernard
>             Fix For: 3.2.0.Beta3
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira