Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/564
Just to add I'm thinking of incorporating ContextualTransform support once
Variable Registry is incorporated to provide the transformation access to
system/env properties, flow file attributes,
GitHub user jfrazee opened a pull request:
https://github.com/apache/nifi/pull/565
NIFI-2090 Add support for HL7 segment names and components in
ExtractHL7Attributes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jfrazee/nifi
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/561
@jvwing Thanks for scoping it out and apologies on the prior false start.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/561
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/561
The update looks good to me. I was able to install, start, stop, reboot,
etc. No test or contrib-check issues. I will squash and merge shortly.
Thanks @apiri for the script and
GitHub user YolandaMDavis opened a pull request:
https://github.com/apache/nifi/pull/564
NIFI-2020 - Enhance JoltTransformJSON processor to support custom transforms
This is the initial commit to enhance the JoltTransformJSON processor by
providing the ability to support custom
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/563
NIFI-2078: External state management.
- Added ExternalStateManager to handle components' state managed
externally
- Added UI codes to display external state
- Added view/clear
Andre,
Sounds good. I suspect we can find some value there so if you're willing
to take up the task, would you be willing to perhaps open up a JIRA? We can
move this discussion to there and kind of flesh out what it might look
like. As mentioned, I think the case, and its ilk, is a common
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/561
Made those fixes and pushed them in a separate commit. Thanks for catching!
Verified this script as committed in a Docker container as opposed to my
prior Frankenscript and it seems to behave
Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi/pull/561#discussion_r68160177
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/bin/nifi.sh
---
@@ -142,22 +138,72 @@ init() {
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/561
@jvwing Drat. I left off the semicolons. I was doing some adjustments in
one of my VM instances and must not have propagated back to my core checkout.
Will update that concerning the || conditionals.
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/548
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Ryan,
I ran into a similar issue, in that our security policies generally don't
allow sudo for much... even for the root account in an init script. I
didn't want to hack up the nifi.sh script too much, so I just popped out a
quick systemd unit file:
[Unit]
Description=Apache NiFi
Github user YolandaMDavis closed the pull request at:
https://github.com/apache/nifi/pull/553
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user YolandaMDavis commented on the issue:
https://github.com/apache/nifi/pull/553
@jvwing @apiri closing out this PR, @apiri has a version coming.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user apiri commented on the issue:
https://github.com/apache/nifi/pull/553
Looks like the current commit will currently disregard nifi-env.sh after
being installed. Consider the case where I install the service and then later
switch JRE (perhaps between Oracle and Open JDK).
Github user jvwing commented on the issue:
https://github.com/apache/nifi/pull/553
Thanks for the update, @YolandaMDavis. I tested this on Amazon Linux, and
it worked well. Service installed, started, restarted after a reboot, stopped,
etc. I was worried that the magic chkconfig
I see these warnings in logs, some records were converted though , but is
there a way to really know what happened, I mean to see the input and then
really see an exception ?.Please advice.
2016-06-22 13:52:43,563 WARN [Timer-Driven Process Thread-91]
o.a.n.processors.kite.ConvertJSONToAvro
thanks man.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/KITESDK-fails-creation-of-schema-tp12105p12119.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/556
Ah sorry @jskora for misinterpreting it, changes look good. I am gonna do
another round of testing and then should be good to merge.
---
If your project is set up for it, you can reply to this
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall I do agree with @jskora interpretation fwiw.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Hi Pradeep,
I don't think ConvertJsonToAvro supports choosing fields. I think you would
have to prepare the JSON the way you want it before this processor.
The easiest way would probably be to use EvaluateJsonPath to extract some
fields to attributes, then AttributesToJson to make a new JSON
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/556
I took @joewitt's comment to mean keeping the combined bundle and
documenting that attributes are not stable and could change with version
upgrades, which will apply to both bundles if we break them
That makes sense. You may want to take into consideration the following
lifted from the spec:
The name portion of a fullname, record field names, and enum symbols must:
- start with [A-Za-z_]
- subsequently contain only [A-Za-z0-9_]
Thus, you may want to replace any other characters
I probably will replace incoming json text "Blah_bc_sc-status" to
"Blah_bc_sc_status" and then operate on it,
THanks
Pradeep
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/KITESDK-fails-creation-of-schema-tp12105p12113.html
Sent from the Apache NiFi
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/558
+1 LGTM, tested with plenty of provenance events, verified the "Skipping
search" entry appeared in the log.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/558
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
awesome, thanks Andrew.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/KITESDK-fails-creation-of-schema-tp12105p12110.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/556
@jskora what about changing it so there is a media and image bundles?
Reading this comment[1] it's what we decided and the only way not to break
backwards compatibility.
[1]
Hi Afsar,
It appears that when you were running the installation, your machine was unable
to connect to the Maven Repository in order to download the necessary
dependencies.
You can troubleshoot connecting to the repository using these steps [1].
[1] http://stackoverflow.com/a/30111316/70465
Hi Pradeep,
That error is due to "-" being an illegal character for an Avro name, per
the spec here[1]. Unfortunately the error message is not as descriptive as
it could be.
Thanks,
Andrew
[1] https://avro.apache.org/docs/1.7.7/spec.html#Names
On Wed, Jun 22, 2016 at 12:02 PM, pradeepbill
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/556
Just pushed final cleanup, that should be it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
if my JSON has "Blah_bc_sc-status":"407" , I can not create a valid schema
using kiteSDK , fails saying
[parumalla@sxmn5 ~]$ ./kite-dataset json-schema --class BCSchemaClass
hdfs:/user/parumalla/test_bc.txt --output
hdfs:/user/parumalla/nifi/schemas/bc.avsc
Unknown error: Illegal character
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/556
According to the latest comment from @bbende, yes
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Thanks Joe, I could not respond back soon, because I was verifying and
validating the details from this post.
You said, ConvertJSONtoAvro at 270 messages per second and ReplaceText is
processing at 70 messages per second.
>How did you do the math here ?
StoreInKite is doing very very little.
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/556
The only relevant exception I saw processing the download folder was an xml
parse error related to a underlying limitation of Tika, no need to address:
2016-06-22 11:32:19,774 ERROR
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/556
nice work on wrapping this stuff up @jskora and @JPercivall !
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/550
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/556
To wrap this up, should I add the failure provenance now or will that be a
future change?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/550
+1 LGTM, reproduced the error then applied the patch and retested, verified
that a connection cannot be moved if its destination has active threads (even
if stopped).
---
If your project is set up
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall @joewitt I believe what you said to be accurate. The JIRA that
I was referencing is https://issues.apache.org/jira/browse/NIFI-104 - I do
believe it is very advantageous to be able to
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall @markap14 here is my two cents in reading this exchange. Joe's
points are really good about what a user expects and would like to see. Mark's
points are true but from a purely how it is
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall the reason is not to keep data in the flow. The reason is
because users often configure the dataflow in that way, and NiFi should handle
that case well. We do have some JIRAs to make
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/556
@markap14 it seems odd to limit the usefulness of provenance for the reason
to "keep data in the flow". Information is being created on "why this flowfile
failed" but we don't track it in
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall we don't typically recommend emitting ROUTE events when routing
to failure. Often times, failure is routed back to self, if for no other reason
than to keep the data in the flow. We don't
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/477
@mattyb149 Looks good for the most part. I left a few inline comments, just
some tweaks that i think can probably help to cleanup the code. Also, I noticed
OrcFlowFileWriter.java is a pretty hefty
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/556
I am trying to parse my downloads folder again and I came across a couple
exceptions (will post in other comment) but as I try to figure why it happened
I realize that since ExtractMediaMetatadata
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68076407
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user bbende commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68075384
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68074816
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/util/orc/OrcUtils.java
---
@@ -0,0 +1,443 @@
+/*
+ *
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68074551
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/util/orc/OrcUtils.java
---
@@ -0,0 +1,443 @@
+/*
+ *
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68074457
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/util/orc/OrcUtils.java
---
@@ -0,0 +1,443 @@
+/*
+ *
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68074121
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68073833
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/util/orc/OrcUtils.java
---
@@ -0,0 +1,443 @@
+/*
+ *
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68073525
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/util/orc/OrcUtils.java
---
@@ -0,0 +1,443 @@
+/*
+ *
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68073235
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68073301
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68072879
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68072906
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68072854
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68072328
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68071005
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/477#discussion_r68070933
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ConvertAvroToORC.java
---
@@ -0,0 +1,303 @@
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68070698
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/556
@JPercivall and @joewitt, I just pushed the updates. Have at it!
* Code review cleanup.
- Replace deprecated ProcessorLog with ComponentLog and deprecated
ObjectHolder with
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/556
I'm running contrib check and a functional test now.
Should be pushed shortly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Aldrin,
On Wed, Jun 22, 2016 at 12:24 AM, Aldrin Piri wrote:
> Concerning the ParseKV, are you aware of the getDelimitedField[1] function
> in Expression Language? I think this may take care of this case for
> handling these items.
>
I am aware of getDelimitedField but I
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/526
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68056970
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/media/TestExtractMediaMetadata.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68052320
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68044679
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/image/ExtractImageMetadataTest.java
---
@@ -37,7
Github user jskora commented on the issue:
https://github.com/apache/nifi/pull/280
Yes, this should be closed. Done.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user jskora closed the pull request at:
https://github.com/apache/nifi/pull/280
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68044015
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/image/ExtractImageMetadataTest.java
---
@@ -37,7
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68042865
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68042751
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68042689
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68041998
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68041847
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68041768
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/test/java/org/apache/nifi/processors/image/ExtractImageMetadataTest.java
---
@@ -37,7
Github user jskora commented on a diff in the pull request:
https://github.com/apache/nifi/pull/556#discussion_r68039891
--- Diff:
nifi-nar-bundles/nifi-media-bundle/nifi-media-processors/src/main/java/org/apache/nifi/processors/media/ExtractMediaMetadata.java
---
@@ -0,0 +1,311
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/559
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/559
Thanks @scottyaslan!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
83 matches
Mail list logo