[jira] [Commented] (NIFI-5988) GetMongo fails to transfer to failure relationship with invalid database or collection name
[ https://issues.apache.org/jira/browse/NIFI-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830864#comment-16830864 ] Matthew Dinep commented on NIFI-5988: - I have attached a patch file for review that implements methods in the AbstractMongoProcessor similar to checkCollectionNameValidity and checkDatabaseNameValidity found in the MongoDB source, but returning a boolean. These are then called in GetMongo and, if they fail, logs an error and transfers the flowfile to failure. > GetMongo fails to transfer to failure relationship with invalid database or > collection name > --- > > Key: NIFI-5988 > URL: https://issues.apache.org/jira/browse/NIFI-5988 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mike Thomsen >Priority: Major > Attachments: > 0001-NIFI-5988-check-database-and-collection-name-validit.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > Invalid Database/Collection names: If GetMongo is configured with invalid > DatabaseName/CollectionName, it doesn't log any ERROR as bulletin or in log > file and also doesn't route to failure relation. It should route to failure > with some Error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5988) GetMongo fails to transfer to failure relationship with invalid database or collection name
[ https://issues.apache.org/jira/browse/NIFI-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830863#comment-16830863 ] Matthew Dinep commented on NIFI-5988: - [^0001-NIFI-5988-check-database-and-collection-name-validit.patch] > GetMongo fails to transfer to failure relationship with invalid database or > collection name > --- > > Key: NIFI-5988 > URL: https://issues.apache.org/jira/browse/NIFI-5988 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mike Thomsen >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > Invalid Database/Collection names: If GetMongo is configured with invalid > DatabaseName/CollectionName, it doesn't log any ERROR as bulletin or in log > file and also doesn't route to failure relation. It should route to failure > with some Error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5988) GetMongo fails to transfer to failure relationship with invalid database or collection name
[ https://issues.apache.org/jira/browse/NIFI-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757587#comment-16757587 ] Mike Thomsen commented on NIFI-5988: [~sivaprasanna] invalid names like @#RQ#%$@ or such. Mongo will automatically create databases and collections on the fly as you need them, so I know that's not an issue. > GetMongo fails to transfer to failure relationship with invalid database or > collection name > --- > > Key: NIFI-5988 > URL: https://issues.apache.org/jira/browse/NIFI-5988 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mike Thomsen >Priority: Major > > Invalid Database/Collection names: If GetMongo is configured with invalid > DatabaseName/CollectionName, it doesn't log any ERROR as bulletin or in log > file and also doesn't route to failure relation. It should route to failure > with some Error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5988) GetMongo fails to transfer to failure relationship with invalid database or collection name
[ https://issues.apache.org/jira/browse/NIFI-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16757552#comment-16757552 ] Sivaprasanna Sethuraman commented on NIFI-5988: --- [~mike.thomsen] Here invalid db/collection name means, non-existing db/collection or names with special characters or both? > GetMongo fails to transfer to failure relationship with invalid database or > collection name > --- > > Key: NIFI-5988 > URL: https://issues.apache.org/jira/browse/NIFI-5988 > Project: Apache NiFi > Issue Type: Bug >Reporter: Mike Thomsen >Priority: Major > > Invalid Database/Collection names: If GetMongo is configured with invalid > DatabaseName/CollectionName, it doesn't log any ERROR as bulletin or in log > file and also doesn't route to failure relation. It should route to failure > with some Error message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
