You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/03 03:29:00 UTC
[jira] [Commented] (NIFI-5102) MarkLogic DB Processors
[ https://issues.apache.org/jira/browse/NIFI-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461883#comment-16461883 ]
ASF GitHub Bot commented on NIFI-5102:
--------------------------------------
GitHub user vivekmuniyandi opened a pull request:
https://github.com/apache/nifi/pull/2671
NiFi-5102 - Adding Processors for MarkLogic DB
…tMarkLogic
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:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Yes, there is a JIRA ticket - https://issues.apache.org/jira/browse/NIFI-5102
- [x] 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.
Yes
- [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
Yes
- [x] Is your initial contribution a single, squashed commit?
No
### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
Yes, but certain tests from other processors fail - such as from grpc processors were failing with an unapproved license error for auto-generated files in the target folder.
- [x] Have you written or updated unit tests to verify your changes?
Yes
- [x] 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)?
Yes
- [x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
No
- [x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
Yes
Have added a NOTICE file and a LICENSE file under the nifi-marklogic-bundle project
- [x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
Yes
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in which it is rendered?
Yes
### 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/marklogic/nifi nifi-5102
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2671.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 #2671
----
commit 16f8ffef0e0a853535c5af63b7e28441b4674c47
Author: Vivek Siddharthan Muniyandi <vm...@...>
Date: 2018-05-03T03:01:25Z
NIFI-5102 Adding MarkLogic DB NiFi processors - QueryMarkLogic and PutMarkLogic
commit e7b4bee69b6bd6a5274613ff884625a9d30b5ffb
Author: Vivek Siddharthan Muniyandi <vm...@...>
Date: 2018-05-03T03:26:14Z
NIFI-5102 Added displaynames for Properties
----
> MarkLogic DB Processors
> -----------------------
>
> Key: NIFI-5102
> URL: https://issues.apache.org/jira/browse/NIFI-5102
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 1.6.0
> Reporter: Anthony Roach
> Priority: Major
> Fix For: 1.7.0
>
>
> As a data architect, I need to ingest data from my NiFi FlowFile into MarkLogic database documents. I have created the following two processors:
> * PutMarkLogic: Ingest Flowfile into MarkLogic database documents
> * QueryMarkLogic: Retrieve result set from MarkLogic into FlowFile
> I will create a pull request.
> [www.marklogic.com|http://www.marklogic.com/]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)