The connector itself encodes binary documents and sends them to ES, purportedly for the mapper attachment to process and convert to text. The test used to exercise that.
Perhaps it's worth reviewing the connector code itself to see what is outdated/legacy, and only test the parts that are not outdated? Specifically, my concern is that we need to support binary document transmission to ES, and ES obviously needs to handle those for the integration to work properly. Karl On Wed, Apr 29, 2020 at 7:27 AM Michael Cizmar <mich...@michaelcizmar.com> wrote: > There's been some changes to Elasticsearch like reducing the document types > and ingestion/mapper. The mapper attachment I believe has been > deprecated in favor of: > > > https://www.elastic.co/guide/en/elasticsearch/plugins/master/ingest-attachment.html > > This should be incorporated into a pipeline. Do we need something like > this in our integration test? I don't think it's the responsibility of the > output connector to handle this. > > On Wed, Apr 29, 2020 at 5:25 AM Karl Wright <daddy...@gmail.com> wrote: > > > Hello all, > > > > I set up a branch (branches/CONNECTORS-1639) to work on the elasticsearch > > test problem for JDK 11. The branch downloads an ES and a mapper > > attachment but it turns out that the mapper attachment is apparently > > incompatible with the current (7.x) version of ES. Does anyone know > > whether the mapper attachment is still supported? If so, where can I > find > > it in the Maven repo? > > > > Karl > > >
