[
https://issues.apache.org/jira/browse/NIFI-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15959470#comment-15959470
]
ASF GitHub Bot commented on NIFI-1280:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/1652
NIFI-1280: Renamed FilterCSVColumns to QueryFlowFile; introduced readers
and writers as controller services
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/markap14/nifi NIFI-1280
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1652.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 #1652
----
commit 4a10c7826051a85d8fab506a76cfc4144d483f0c
Author: Toivo Adams <[email protected]>
Date: 2016-05-07T09:29:15Z
NIFI-1280 Create FilterCSVColumns Processor.
commit 4f262960dcd4e17bc77c78b50c979c3717ab40ec
Author: Mark Payne <[email protected]>
Date: 2016-07-11T18:57:00Z
NIFI-1280: Refactoring to make more generic so that other data types can be
supported; created InputStreams to content on-demand so that multiple passes
can be made over FlowFile content if required. Created new Controller Services
for reading and writing specific data types
commit 9def3d90374025a8e7172ac6d014f7b0ac644c4d
Author: Oleg Zhurakousky <[email protected]>
Date: 2017-03-30T13:12:07Z
NIFI-1280 added support for RecordSchema in SchemaRegistry
Signed-off-by: Mark Payne <[email protected]>
commit f1b061988352bd556b4a7a49afaf777c7be95315
Author: Mark Payne <[email protected]>
Date: 2017-03-30T14:19:54Z
NIFI-1280: Updated SimpleKeyValueSchemaRegistry to make use of new CHOICE
RecordFieldType
- Update Record Readers to use SchemaRegistry controller service. Moved
SchemaRegistry api into its own maven module and added to standard-services-api
so that we can properly add dependencies on it. Code cleanup and bug fixes
----
> Create QueryFlowFile Processor
> ------------------------------
>
> Key: NIFI-1280
> URL: https://issues.apache.org/jira/browse/NIFI-1280
> Project: Apache NiFi
> Issue Type: Task
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.2.0
>
>
> We should have a Processor that allows users to easily filter out specific
> columns from CSV data. For instance, a user would configure two different
> properties: "Columns of Interest" (a comma-separated list of column indexes)
> and "Filtering Strategy" (Keep Only These Columns, Remove Only These Columns).
> We can do this today with ReplaceText, but it is far more difficult than it
> would be with this Processor, as the user has to use Regular Expressions,
> etc. with ReplaceText.
> Eventually a Custom UI could even be built that allows a user to upload a
> Sample CSV and choose which columns from there, similar to the way that Excel
> works when importing CSV by dragging and selecting the desired columns? That
> would certainly be a larger undertaking and would not need to be done for an
> initial implementation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
