[
https://issues.apache.org/jira/browse/NIFI-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412692#comment-16412692
]
ASF GitHub Bot commented on NIFI-4516:
--------------------------------------
Github user MikeThomsen commented on the issue:
https://github.com/apache/nifi/pull/2517
> Is that what you meant with integration tests? What do you mean with
FetchSolrIT? Do you have a link for an example?
You would create a JUnit test called `FetchSolrIT` and follow the model
used in the MongoDB processors and others (ex. `PutMongoRecordIT`). It's a
JUnit test that assumes a live instance of Solr and runs against that instead
of mocks. If you name it `FetchSolrIT` instead of `FetchSolrTest` it will skip
normal maven surefire execution and only run when the user wants it to run.
That can be done with:
`mvn clean integration-test -Pintegration-tests`
> Add FetchSolr processor
> -----------------------
>
> Key: NIFI-4516
> URL: https://issues.apache.org/jira/browse/NIFI-4516
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Johannes Peter
> Assignee: Johannes Peter
> Priority: Major
> Labels: features
>
> The processor shall be capable
> * to query Solr within a workflow,
> * to make use of standard functionalities of Solr such as faceting,
> highlighting, result grouping, etc.,
> * to make use of NiFis expression language to build Solr queries,
> * to handle results as records.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
