Paul,
Your comments regarding the accuracy of the expression language documentation
were in a different message, so it’s entirely possible and likely that Matt has
not seen them yet. In general, when a member of the team or community has
responded to a message, the remainder of the community do
Thanks for responding, however...
Your expression below evaluates to true if IT IS NOT THE CASE THAT ALL THREE
ATTRIBUTES ARE EMPTY.
But I need an expression that evalutes to true if IT IS THE CASE THAT ALL THREE
ATTRIBUTES ARE NOT EMPTY.
There are two entirely different things.
T
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/296
---
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 enable
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57103757
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/PutKafka.java
---
@@ -371,11 +371,12 @@ private
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57096148
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/KafkaPublisher.java
---
@@ -104,21 +128,52 @
I’ve also created a ticket [1] for the documentation improvements so you can
follow the progress on that. As this is an open source project, submissions are
always welcomed as well. You can follow the steps in the contributor guide [2]
and quickstart guide [3] for guidance on submitting a pull r
Thanks Paul.
Bugs and feature requests can be submitted here [1] which will ensure they are
seen by the entire team/community. The most helpful reports include screenshots
when applicable, current system description, and potential use cases or unit
tests to verify issue resolution.
Very quickl
Great.
I can tell you a list of things I think need to be improved in NiFi. The most
important is having two “modes” that one is always in, an “edit mode”, which is
basically what you have 100% of the time now, and a “non-edit mode”, where the
user cannot move things (inadvertently) around o
Thanks Paul. We always welcome feedback that helps us improve the product and
documentation. I can’t promise those documentation fixes will be released in
0.6.0 but we will try to get them out as soon as possible.
Andy LoPresto
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57087522
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/PutKafka.java
---
@@ -371,11 +371,12 @@ priv
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/294#issuecomment-23951
@markap14 Proposed commit for my comments [1]. If this looks good to you,
I'll include them in your PR.
[1]
https://github.com/mcgilman/nifi/commit/9796e7620cb06
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/299
---
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 enable
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/299#issuecomment-199973350
Build and contrib check is good. Verified functionality with time zone on
formatted date string, new time field strategy, state clearing issue, and start
time to eliminat
Github user mattyb149 closed the pull request at:
https://github.com/apache/nifi/pull/298
---
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 ena
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/298#issuecomment-199960791
+1
Reviewed the code, did a contrib check build and verified the functionality
in a NiFi instance against ES 2.1.1.
---
If your project is set up for it, you
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57044106
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/Partitioners.java
---
@@ -0,0 +1,87 @@
+
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/299#issuecomment-199951509
Reviewing...
---
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
en
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/299
NIFI-1420 Fixing minor bugs in GetSplunk
- Adding a Time Zone property so the Managed time ranges use the provided
time zone when formatting the date strings
- Adding a Time Field Strategy property
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57040700
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/Partitioners.java
---
@@ -0,0 +1,87 @@
+/*
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/297
---
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 enable
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57040041
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/PutKafka.java
---
@@ -446,444 +336,136 @@ prote
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57039809
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/KafkaPublisher.java
---
@@ -0,0 +1,159 @@
+
Bryan, Matt,
Both of these seem pretty straightforward and would be nice to capture as
well while the Kafka tickets are resolved.
Thanks for the notice!
Current status has us looking at the following before I create RC2:
NIFI-1664
NIFI-1645
NIFI-1665
NIFI-1420
NIFI-1666
On Tue, Mar 22, 2016 at
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199945870
Great, thanks everyone for scoping this out. I'll merge those exclusions
in with my commit and get them off to master.
---
If your project is set up for it, you can reply
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199945136
+1
The build looks good in both OSX and Windows 10.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Pierre,
The error message is really strange. It appears that a number of classes
did not compile correctly. Was there any unexpected output during the maven
build? I just verified the build locally on OSX and Windows 10. In Windows
10 I copied the zip, extracted, and executed run-nifi.bat without
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/298
NIFI-1666: Fixed bug with EL evaluation in PutElasticsearch processor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi NIFI-1666
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199939742
+1
Reviewed the code and did a contrib check build on Windows 8, looks good.
---
If your project is set up for it, you can reply to this email and have your
re
All,
We found an issue with the PutElasticsearch processor as well, it doesn't
evaluate EL expressions using the flow file attributes for the Index and
Document Type properties. This is a simple fix, I've written it up as
NIFI-1666 [1] and will have a PR very shortly. I'd like to get this into
0.6
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199936658
With the added pom exclusions the build passes
---
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 p
Hi Aldrin,
I agree that an enhancement to the existing processor could fulfill the same
goal. My thinking was that adding to the EL would essential add the
functionality to all processors that support the EL. Of course the adding to
the EL does not mean that the existing processor could not b
Thanks, Matt, Glad to see I was on the right track, even before your email. I
think its testament to great organization and clarity of the existing code.
Cheers,
Chris
On 3/22/16, 12:45 PM, "Matt Burgess" wrote:
>Chris,
>
>Great to hear! For the following steps, I'm assuming it will be a
All,
While testing the original RC I came across a couple of issues with the new
GetSplunk processor.
The first issue relates to being able to specify the timezone through a
processor property, so that the timezone used for searching will match with
splunk's timezone.
The second is is that GetSpl
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57026907
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/PutKafka.java
---
@@ -446,444 +336,136 @@ pr
Chris,
Awesome that you are ready to dive in and get this fixed up. The
functionality is certainly one that would be helpful.
I do find myself a bit torn on whether the inclusion of this as EL is
preferred instead of the extension of EvaluateJsonPath as suggested
in NIFI-1567 [1]. Are there use
Chris,
Great to hear! For the following steps, I'm assuming it will be a
one-argument function called "jsonPath" that takes a String containing a
JSON Path expression to be evaluated on the "subject" of the function. So I
am picturing it used like:
${ my.json.attribute:jsonPath("$.path.to.my.data
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199897484
Not sure why this came up, but have included it in
a2e679bbbc4f612a9fc61a51d47aba693789a44b. If that checks out, I can squash
this with the actual changes.
---
If your pr
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199894397
I am seeing the same contrib check failure that @JPercivall mentioned above
running Windows 10.
> Unapproved licenses:
>
>
C:/Users/gilman/Documents/s
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57019067
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/Partitioners.java
---
@@ -0,0 +1,87 @@
+
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57018795
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/Partitioners.java
---
@@ -0,0 +1,87 @@
+
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57017510
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/KafkaPublisher.java
---
@@ -0,0 +1,159 @@
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199890235
I can add this as part of the commit. Did everything else check out okay
though?
---
If your project is set up for it, you can reply to this email and have your
reply appe
Github user jvwing commented on a diff in the pull request:
https://github.com/apache/nifi/pull/267#discussion_r57017952
--- Diff:
nifi-nar-bundles/nifi-iaa-providers-bundle/nifi-file-identity-provider/src/main/java/org/apache/nifi/authentication/file/FileIdentityProvider.java
---
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199888509
A very weird error with contrib check I am only getting windows 8, an
unapproved license for:
nifi/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/sr
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57016835
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/KafkaPublisher.java
---
@@ -0,0 +1,159 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57015759
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/KafkaPublisher.java
---
@@ -0,0 +1,159 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/295#discussion_r57015299
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/processors/kafka/KafkaPublisher.java
---
@@ -0,0 +1,159 @@
Joe,
Looking through the associated tickets, both sound like worthwhile
additions and can hold off until those items get through reviews.
--Aldrin
On Tue, Mar 22, 2016 at 11:47 AM, Joe Witt wrote:
> Aldrin,
>
> NIFI-1665 appears to correct a problematic behavior when pulling from
> Kafka and w
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199871907
Testing on Windows 7
---
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
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199874747
I'm a +1, all tests previously in failure are now OK.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Aldrin,
NIFI-1665 appears to correct a problematic behavior when pulling from
Kafka and when timeouts can occur. Definitely think we should get
this in the build. I also see that NIFI-1645 is up and given the
trouble that is causing for use of delimiter function we should engage
on this.
Since
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199870316
I am testing on Windows 8.
---
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 folks,
I’m a newbie NiFi user but long time Java developer. I’ve entered a Jira issue
to extend the expression language to add a function to evaluate a Json path
against the subject. Looking at the code I feel this is very doable, and I am
up for task so I’m planning on tackling it. I’ve
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/297#issuecomment-199867101
I can verify the tests on Windows 10.
---
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
GitHub user apiri opened a pull request:
https://github.com/apache/nifi/pull/297
NIFI-1664 Preferring System.nanoTime to System.currentTimeMillis and â¦
â¦providing explicit handling of timestamps for files in those tests that
are testing other attributes of the ListFile process b
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/296
NIFI-1665 fixed GetKafka to reset consumer in case of timeout
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1665
Alternatively yo
Paul,
You can achieve what you are trying to do by using the not function.
let assume the attributes you want to check to make sure they have a vlaue
set are attr1, attr2, and attr3.
The expression would be
*${allAttributes('attr1','attr2','attr3'):isEmpty():not()}*
Thanks,
Matt
On Tue, Mar
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/295
NIFI-1645 refactored PutKafka
- used newest API available in 0.8.* version
- added PutKafka integration tests
- Kafka module code coverage is at 85%
NIFI-1645 polishing
You can merge th
I did a full build with Maven, took the generated zip
(nifi-0.6.0-SNAPSHOT-bin.zip), unzipped it, and executed the run-nifi.bat.
So it is a clean instance. As you said, the local-provider is correctly set:
local-provider
org.apache.nifi.controller.state.providers.local.WriteAheadLoca
Pierre,
Are you attempting to upgrade an existing instance? If so, what version are
you coming from? I'm wondering if there is some configuration missing after
the upgrade. Are you able to start up the built assembly using default
configuration?
In your /conf/state-management.xml can you verify t
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/294#issuecomment-199837163
Also, in nf-cluster-search.js we can delete line 72 and 172. We no longer
need to set:
`nf.SummaryTable.systemDiagnosticsUrl`
Setting the clusterNodeId o
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/294#issuecomment-199835774
@markap14 Unfortunately, the changeset is too big for me to comment on
directly. But in nf-counters-table.js the Ajax request on line 281 does not
need to set the nodewis
OK. Logs are here:
https://raw.githubusercontent.com/pvillard31/share/master/nifi-app.log
2016-03-22 15:12 GMT+01:00 Matt Burgess :
> I can't see them, perhaps the attachment is being removed. Can you paste
> the text from the logs into the email?
>
> Thanks,
> Matt
>
> On Tue, Mar 22, 2016 at 10
I can't see them, perhaps the attachment is being removed. Can you paste
the text from the logs into the email?
Thanks,
Matt
On Tue, Mar 22, 2016 at 10:10 AM, Pierre Villard <
pierre.villard...@gmail.com> wrote:
> Erf that's strange, I do see logs from my side.
> Is it better?
>
> 2016-03-22 15:
Erf that's strange, I do see logs from my side.
Is it better?
2016-03-22 15:06 GMT+01:00 Oleg Zhurakousky :
> Pierre, no logs ;)
>
> > On Mar 22, 2016, at 10:03 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
> >
> > Hi,
> >
> > I updated my local checkout to current master and did a s
Pierre, no logs ;)
> On Mar 22, 2016, at 10:03 AM, Pierre Villard
> wrote:
>
> Hi,
>
> I updated my local checkout to current master and did a successful maven
> build. When trying to start generated binaries, I have a bunch of errors and
> NIFI does not start. See attached logs.
>
> Does s
Hi,
I updated my local checkout to current master and did a successful maven
build. When trying to start generated binaries, I have a bunch of errors
and NIFI does not start. See attached logs.
Does someone experience the same issue?
Thanks,
Pierre
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/294#discussion_r56988394
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/CounterDTO.java
---
@@ -98,4 +98,12
https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#isempty
Why don't you have function "notEmpty"? This would be useful when combined with
"allAttributes".
I can't see any way, with your current set of functions, to determine that all
of a set of attributes are not empt
All,
Given the issues I am cancelling this vote. There were some miscues in the
artifact generation process that have caused issues and clouded the
process. Please look for an updated vote RC and helper.
Thank you for your efforts and time and apologies for the hiccups.
On Tue, Mar 22, 2016 at
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/294#discussion_r56984358
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-client-dto/src/main/java/org/apache/nifi/web/api/dto/CounterDTO.java
---
@@ -98,4 +98,12
I'm looking at:
https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html
> isEmpty
Description: The isEmpty function returns true if the Subject is null or
contains only white-space (new line, carriage return, space, tab), false
otherwise.
This logically implies that isEmpty
Drat, the announce email was wrong (likely glossed over it copying and
pasting), but the md5sum provided to the repository is correct
( nifi-0.6.0-source-release.zip.md5). I did an md5 against the artifact as
provided to SVN using the actually prepared md5 checksum.
# apiri in ~/Development/verify
I'm getting an MD5 checksum mismatch on the ZIP:
< MD5(nifi-0.6.0-source-release.zip)= 1559157db000d53221aeabc5dd607cfc
---
> MD5(nifi-0.6.0-source-release.zip)= 1597a93574b928b7c78e3014d1eca416
On Mon, Mar 21, 2016 at 11:08 PM, Andy LoPresto
wrote:
> Thanks to Aldrin and Matt Burgess, we were
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-199714780
@taftster Thanks Adam. I updated the PR regarding your comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
75 matches
Mail list logo
