[ 
https://issues.apache.org/jira/browse/NIFI-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16436188#comment-16436188
 ] 

ASF GitHub Bot commented on NIFI-4516:
--------------------------------------

Github user JohannesDaniel commented on the issue:

    https://github.com/apache/nifi/pull/2517
  
    @MikeThomsen Thank you for your help with Git!!
    @bbende 
    - Solr core is a test dependency again (I actually had a reason to add this 
as a non-test dependency, but it was not a good reason...)
    - Processor is now called QuerySolr
    - I added the common parameters for Solr as properties (except fq). For 
those parameters that can be set multiple times, I adopted your logic of 
PutSolrContentStream. These parameters can be added as dynamic properties, e. 
g. fq.1=field:value and fq.2=field:value. I inserted this method into SolrUtils 
and adjusted the pattern a little bit (parameters containing dots are also 
allowed now, e. g. facet.field). However, we could consider to allow even more 
characters. Currently, only word characters and dots are allowed. The Solr 
committers highly recommend to name fields only with these characters, but it 
is not mandatory. Probably, a pattern like ".*\.\d+$" would be more suitable.
    - I made it configurable whether the processor only returns top results 
(for one request in a single flowfile) or full result sets (for multiple 
requests in multiple flowfiles with rows as batch size). In the latter case, 
the processor pages through the results. Additionally, the cursor mark for 
responses is added as attribute, so users principally should be enabled to 
build their own looping via dataflows.


> 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)

Reply via email to