You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Chris Sampson (Jira)" <ji...@apache.org> on 2022/10/17 13:26:00 UTC
[jira] [Comment Edited] (NIFI-3124) Test code cleanup in ElasticSearch (2.x API) processors
[ https://issues.apache.org/jira/browse/NIFI-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618811#comment-17618811 ]
Chris Sampson edited comment on NIFI-3124 at 10/17/22 1:25 PM:
---------------------------------------------------------------
These all now appear to have been removed.
NIFI-10437 also moved to using Testcontainers for running Elasticsearch within Docker as part of the Integration Tests for the {{nifi-elasticsearch-client-service}}, so the same approach could be used in other modules if required in future.
was (Author: chris s):
These all now appear to have been removed.
NIFI-10473 also moved to using Testcontainers for running Elasticsearch within Docker as part of the Integration Tests for the {{nifi-elasticsearch-client-service}}, so the same approach could be used in other modules if required in future.
> Test code cleanup in ElasticSearch (2.x API) processors
> -------------------------------------------------------
>
> Key: NIFI-3124
> URL: https://issues.apache.org/jira/browse/NIFI-3124
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Jeff Storck
> Priority: Minor
>
> Tests that are marked with @Ignore due to their integration nature should be moved into integration tests classes.
> Also, the current integration tests in ITQueryElasticsearchHttp and ITScrollElasticsearchHttp should be updated to not assume hostnames and existing data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)