Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/232#issuecomment-212772606
@pvillard31 I squashed and merged; also backported the changes to 0.x (and
I think I got it right this time). Thanks for the contributions.
---
If your project is set
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/232
---
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 adamonduty commented on the pull request:
https://github.com/apache/nifi/pull/256#issuecomment-212741812
@mattyb149 I really appreciate your comments on this PR. My free time is a
bit limited this week, but let me get back to you in a few days.
---
If your project is set
I would support option 4, then option 1. I think this is a significant change,
so backward-compatibility is important, and I don’t see specifying the return
type to be a high hurdle provided the documentation is clear. If someone is
writing in expression language, there is a minimum expectation
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/373
---
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
Hello Dev list,
I've been working on a couple improvements that deal with utilizing expression
language to do data analysis and this has exposed a couple issues with the
typing of numbers in Expression Language (EL). The improvements are a
continuation of the topic I presented on at the Apache N
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/373#issuecomment-212696238
Mistyped the Jira -- should be NIFI-1789. Will amend commit.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
GitHub user alopresto opened a pull request:
https://github.com/apache/nifi/pull/373
NIFI-1795 Temporarily ignored incorrectly failing test
TestPutUDP#testUnknownHostname.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alopresto/
Github user asfgit closed the pull request at:
https://github.com/apache/nifi-minifi/pull/14
---
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
Hi Keith,
I’ve moved this conversation to the dev list as that is where coding is more
frequently discussed as opposed to the users list. If you’re not already
subscribed, you can do so following the instructions here [1] to ensure you see
any replies.
The best approach is probably to examine
Bryan,
That is a good point and I do think we should avoid putting such a
rule/requirement in place. However, practically speaking I would
imagine that is how it will play out most often.
I've taken the comments of this thread largely based on Tony's
excellent start and created a draft wiki page
Team,
There have been a couple lively threads on the subject [1][2] and we
need to get these things documented so we have some shared framework
to work from and we can tweak as needed. I've tried to distill the
discussion in [1] and [2] and captured from our recent practices the
model as it is to
Team,
Lots of great movement going and now we're working towards the new 1.x
line while also continuing progress on the 0.x line. While we
progress just be mindful that 0.x is committed to working against Java
7 as a minimum whereas 1.x is Java 8 as a minimum. When merging PRs
to both lines just
GitHub user apiri opened a pull request:
https://github.com/apache/nifi-minifi/pull/14
MINIFI-26 Establishing specific handling of RELOAD events
MINIFI-26 Establishing specific handling of RELOAD events such that
notifiers are not closed on configuration changes.
You can merge thi
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/350#issuecomment-212598568
thanks Oleg. I'd like to review this as part of the larger #366 effort.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
/Note: I omitted a bunch of fields from the JSON document when using the Solr
UI and curl./
I performed additional tests from the UI:
Storing the entire JSON document using the UI resulted in an Http 400 Bad
Request Response. By comparing our JSON document to the Solr schema, I saw
the JSON docu
Github user olegz closed the pull request at:
https://github.com/apache/nifi/pull/350
---
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 enabled
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/350#issuecomment-212597713
Closing it after discussing it with @joewitt. Will be addressed as part of
the https://github.com/apache/nifi/pull/366 PR since there are already
dependency on renaming/ref
Bryan Bende wrote
> Ok so sounds like the incoming JSON is valid, a couple of more questions
> then...
>
> What version of Solr are you using?
We are using Solr 5.2.1.
Bryan Bende wrote
> Can you insert the same JSON document outside of NiFi with success?
>
> In one of the more recent versions
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60475629
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60474620
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60474410
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60474156
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Ok so sounds like the incoming JSON is valid, a couple of more questions
then...
What version of Solr are you using?
Can you insert the same JSON document outside of NiFi with success?
In one of the more recent versions (5.2 or 5.3 maybe), the Solr admin
console added a page to the UI where you c
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60471765
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60471604
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/
Hi Brian,
Yes, the JSON object I am storing is a valid JSON document. The Content
Payload is set to true and the value is:
{"docid":"a1602677-fc7c-43ea-adba-c1ed945ede3d_1831"}
I believe I would have gotten a JSON syntax error saying that the JSON
object was invalid.
--
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60468517
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/PutHiveQL.java
---
@@ -0,0 +1,320 @@
+/*
+
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60468215
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/PutHiveQL.java
---
@@ -0,0 +1,320 @@
+/*
+
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60467879
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/ExecuteHiveQL.java
---
@@ -0,0 +1,172 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60467669
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60467535
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60467301
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60467110
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/372#discussion_r60466456
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/dbcp/hive/HiveConnectionPool.java
---
@@ -0,0 +1,184 @@
+/*
Hello,
Just to clarify, do you have LogAttribute with the "Log Payload" property
to true?
If the actual output of LogAttribute is
/[*docid*="95663ced-6a3b-4356-877a-7c5707c046e7_779"]/
then that is not a valid JSON document.
You would need the content of the flow file to be something like the
fo
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/372
NIFI-981 [REVIEW-ONLY]: Initial addition of HiveQL processors
I'd like to get some feedback on the ExecuteHiveQL and PutHiveQL processors
before I start adding Kerberos support and such. I will inco
While using PutSolrContentStream to store a JSON object in SolrCloud, I've
been running into this issue of being unable to store a document. I've
uploaded a solr schema that says that the field *docid* is required and a
string. Attempting to store a document in solr, this is the error I get:
Faile
Github user tiagodias90 closed the pull request at:
https://github.com/apache/nifi/pull/371
---
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 e
GitHub user tiagodias90 opened a pull request:
https://github.com/apache/nifi/pull/371
PUTSQL error
when I run the "putSQL" he returns me this error:
"2016-04-20 17:13:46,563 ERROR [Timer-Driven Process Thread-8]
o.apache.nifi.processors.standard.PutSQL
PutSQL[id=9f26585
So are we saying as a community that a contributor has to first become a
committer, and then only after continued consistent engagement could then
be considered for PMC?
I don't have any issue with that approach, although it is not exactly what
I thought when we first created the two tiers.
On We
Tony,
There appears to be consensus around these thoughts. Perhaps we
should document this on a Wiki page?
I think generally for committer status it would be good to see a
number of these things for a period of time and then for PMC status to
see those contributions continue and ideally expand f
GitHub user apiri opened a pull request:
https://github.com/apache/nifi/pull/370
NIFI-1654 Creating an initial appveyor.yml file
Adding appveyor.yml to the list of excluded items for RAT check. This
patch successfully integrates our repository with Appveyor and performs a
build, h
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-212463926
@olegz No problem. Currently in London for a training, will try to
test/review it on Friday.
---
If your project is set up for it, you can reply to this email and have
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-212462519
@pvillard31 would be nice (if/when you get time) for you to test and review
this one. Basically we want to try to merge this one as quick as possible so
community get's a ch
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/368
---
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 asfgit closed the pull request at:
https://github.com/apache/nifi/pull/355
---
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 the pull request:
https://github.com/apache/nifi/pull/355#issuecomment-212448324
Just discussed it with @joewitt and will be merging it now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/368#discussion_r60416327
--- Diff:
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/SequenceFileWriterImpl.java
---
@@ -94,8
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/368#issuecomment-212445861
@olegz You are absolutely right! Thanks for the lines of code, added the
test in an existing test class for this.
---
If your project is set up for it, you can reply t
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/369
---
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/369#issuecomment-212440231
Updated URIs look correct. Build, contrib check are good. @markap14 thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/369#issuecomment-212434397
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 markap14 opened a pull request:
https://github.com/apache/nifi/pull/369
NIFI-1790: Updated the URI patterns used in NCM for determining whether or
not responses should be merged
NIFI-1790: Updated the URI patterns used in NCM for determining whether or
not responses sho
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/368#issuecomment-212427393
@pvillard31 I know we have a lot of these "quick-fix-hit-and-run" bugs that
require half a line of code change (and you've been absolutely awesome in
knocking those out alon
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/368#discussion_r60407160
--- Diff:
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/SequenceFileWriterImpl.java
---
@@ -94,8 +94,1
Github user Paul424 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/224#discussion_r60392648
--- Diff:
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/PutDynamoDB.java
---
@@ -0,0 +1,182 @@
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/367
---
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 pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/368#discussion_r60384217
--- Diff:
nifi-nar-bundles/nifi-hadoop-bundle/nifi-hdfs-processors/src/main/java/org/apache/nifi/processors/hadoop/SequenceFileWriterImpl.java
---
@@ -94,8
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/368
NIFI-1788 Fixed listed allowable values
- fixed list of allowable values
- replaced related deprecated method when writing
You can merge this pull request into a Git repository by running:
Github user ToivoAdams commented on a diff in the pull request:
https://github.com/apache/nifi/pull/321#discussion_r60382818
--- Diff: nifi-mock/src/main/java/org/apache/nifi/util/TestRunner.java ---
@@ -865,4 +866,21 @@
* @return the State Manager that is used to store an
Site-to-site is in pretty much every version of nifi released under apache.
> On 20 Apr 2016, at 10:48, Sourav Gulati wrote:
>
> Thanks Simon. Which version of Nifi support site to site?
>
> Regards,
> Sourav Gulati
>
> -Original Message-
> From: Simon Ball [mailto:sb...@hortonworks.co
Thanks Simon. Which version of Nifi support site to site?
Regards,
Sourav Gulati
-Original Message-
From: Simon Ball [mailto:sb...@hortonworks.com]
Sent: Wednesday, April 20, 2016 1:28 PM
To: dev@nifi.apache.org
Subject: Re: Reg: Tailing a remote file
The best way to do this would be to
GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/367
NIFI-1787 fixed typo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-1787
Alternatively you can review and apply these ch
The best way to do this would be to run a nifi agent on the remote system,
using the TailFile processor, and then use site-to-site to get that into your
core nifi.
Simon
> On 20 Apr 2016, at 09:49, Sourav Gulati wrote:
>
> Hi Team,
>
> We want to process logs from a file which is getting u
Hi Team,
We want to process logs from a file which is getting updated continuously on
remote system.
What is the best way to do that in NiFi?
Regards,
Sourav Gulati
NOTE: This message may contain information that is confidential, proprietary,
privileged
66 matches
Mail list logo
