[
https://issues.apache.org/jira/browse/NIFI-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16544300#comment-16544300
]
ASF GitHub Bot commented on NIFI-5305:
--------------------------------------
GitHub user MikeThomsen opened a pull request:
https://github.com/apache/nifi/pull/2891
NIFI-5305 Added a unit test to check for the behavior described in th…
…e bug report because it was not being explicitly checked before.
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [ ] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/MikeThomsen/nifi NIFI-5305
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2891.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2891
----
commit a704700e372f57101a7de9bb586712f108198a74
Author: Mike Thomsen <mikerthomsen@...>
Date: 2018-07-14T18:18:28Z
NIFI-5305 Added a unit test to check for the behavior described in the bug
report because it was not being explicitly checked before.
----
> Parameterized collection name fails with dynamic params
> -------------------------------------------------------
>
> Key: NIFI-5305
> URL: https://issues.apache.org/jira/browse/NIFI-5305
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.6.0
> Reporter: Luis M Calderon
> Assignee: Mike Thomsen
> Priority: Major
> Attachments: getmongo_error.txt
>
>
> When using a dynamic property for collection name, the creation of the full
> query reference name is not working as expected. The reference name seems to
> be the concatenation of the namespace and collection name. i.e.
> _<namespace>.<collection_name>)_
> The following parameters are those which are provided to the GetMongo
> Processor:
> Param Definitions:
> my_schema = 'my_schema'
> collection_name = <dynamic value from a FlowFile attribute>
> {code:java}
> Mongo Database Name: ${my_schema}
> Mongo Collection Name: ${collection_name}{code}
>
> Attached is a text file containing the NiFi log for this error.
>
> _There is no namespace error when the same values are hard coded._
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
