Re: Another Elasticsearch patch to allow the long URI

Hi, Jorn. Jörn Franke wrote: >Maybe use SHA-256 or later. SHA-1 is obsolete and one never knows when it will >be removed from JDK. SHA-1 is used in the ManifoldCF existent class. (org.apache.manifoldcf.core.system.ManifoldCF) If "SHA" is replaced "SHA-256" in this class, the default algorism is

Re: Another Elasticsearch patch to allow the long URI

Maybe use SHA-256 or later. SHA-1 is obsolete and one never knows when it will be removed from JDK. > Am 02.03.2021 um 04:10 schrieb Shirai Takashi/ 白井隆 : > > Hi, there. > > I've found another trouble in Elasticsearch connector. > Elasticsearch output connector use the URI string as ID. >

Another Elasticsearch patch to allow the long URI

Hi, there. I've found another trouble in Elasticsearch connector. Elasticsearch output connector use the URI string as ID. Elasticsearch allows the length of ID no more than 512 bytes. If the URL length is too long, it causes HTTP 400 error. I prepare two solutions with this attached patch. The