[
https://issues.apache.org/jira/browse/NIFI-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021675#comment-16021675
]
Pierre Villard commented on NIFI-3961:
--------------------------------------
The database URL will accept expression language so you could use variables
(starting with 1.3.0 and NIFI-3867). Not sure to understand "we needed to pass
queue name base on flows" though. Do you mean specify a queue based on an
attribute of a flow file being processed, or by a different queue for different
workflows? If the latter, I would create a controller service per workflow. If
that should be per flow file, then that's a different story since the data
source is created only when the controller service is configured. In any case,
you can certainly fire a pull request with your code :)
> HiveConnectionPool with yarn queue settings
> -------------------------------------------
>
> Key: NIFI-3961
> URL: https://issues.apache.org/jira/browse/NIFI-3961
> Project: Apache NiFi
> Issue Type: Wish
> Components: Extensions
> Reporter: Hassan Faouaz
> Priority: Minor
>
> Ability to specify yarn queue when getting a Hive connection. This is one
> example. Possible use the same feature to pass in any parameter to a
> connection string URL as parameter based....
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
