[
https://issues.apache.org/jira/browse/CONNECTORS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305365#comment-17305365
]
Karl Wright commented on CONNECTORS-1666:
-----------------------------------------
r1887840 submits my take on what is necessary to correct the actual problem.
Users do not need to know or care much about the format of the ID ES is using.
Nor is it necessary to use hashing beyond what MCF itself provides and uses
internally for its database keys.
Note that the patches provided also include some updates to the ES API. These
should be discussed and perhaps implemented as well.
> ElasticSearch connector cannot use full URLs for IDs
> ----------------------------------------------------
>
> Key: CONNECTORS-1666
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1666
> Project: ManifoldCF
> Issue Type: Bug
> Components: Elastic Search connector
> Affects Versions: ManifoldCF 2.17
> Reporter: Karl Wright
> Assignee: Karl Wright
> Priority: Major
> Attachments: apache-manifoldcf-2.18-elastic-id.patch,
> apache-manifoldcf-2.18-elastic-id.patch.gz,
> apache-manifoldcf-elastic-id-2.patch,
> apache-manifoldcf-elastic-id-2.patch.gz, apache-manifoldcf-elastic-id.patch,
> apache-manifoldcf-elastic-id.patch.gz
>
>
> The size of the ElasticSearch ID field is severely limited. We therefore
> need to use a strategy to hash the ID when it gets too long so that ES
> doesn't fail on such documents.
> (Patches submitted on behalf of Shirai Takashi)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
