[
https://issues.apache.org/jira/browse/METAMODEL-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161678#comment-14161678
]
Kasper Sørensen commented on METAMODEL-84:
------------------------------------------
1) I don't think this will be a risk. For each Document object in the ES API we
can simply call "getDocumentID()". We do not have to know the physical name.
2) I would go for a STRING type simply.
> Include Document ID (as "_id") in ElasticSearch tables
> ------------------------------------------------------
>
> Key: METAMODEL-84
> URL: https://issues.apache.org/jira/browse/METAMODEL-84
> Project: Metamodel
> Issue Type: Improvement
> Reporter: Kasper Sørensen
>
> I have been trying out the new ElasticSearch module a bit more now ...
> One requirement I would add is: It would be very nice to have the Document
> IDs represented in our table model. The Document IDs can act as primary keys
> which makes it much easier to identify records in the table. It also makes
> sense from a performance point of view since ElasticSearch has a
> high-performance way of doing a document-lookup based on doc ID. We could
> thus implement the executePrimaryKeyLookupQuery(...) method in
> ElasticSearchDataContext and offer such a quick lookup optimization,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
