[
https://issues.apache.org/jira/browse/METAMODEL-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161588#comment-14161588
]
Alberto Rodriguez commented on METAMODEL-84:
--------------------------------------------
This is an interesting topic, but it raises some questions to me.
1. As per the ElasticSearch documentation: "The _id mapping can also be
associated with a path that will be used to extract the id from a different
location in the source document". Does it mean that when we get an element from
a index where the user has defined a specific field to be its index we are not
going to get the _id field anymore? If so, we could not fill the docId column:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-id-field.html
2. Also per the ES doc: "Auto-generated IDs are 22 character long, URL-safe,
Base64-encoded string universally unique identifiers, or UUIDs.". Which
DocumentType should we use for the doc id column??
> 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)
