Andre,
Forgive me for being dense - is that an actual stack trace?
On Wed, Dec 9, 2015 at 2:57 AM, Andre wrote:
> Is anyone having issues running this build?
>
> I can build, however, when I try to run the above on commit in on my on a
> JamaicaVM running on ThreadX but
It doesn't necessarily have to be on the same machine, but the machine NiFi
is on would have to be able to communicate with the name-node and
data-nodes in order to push/pull data to/from HDFS. In your example this
would mean your local machine would need to be able to access the name-node
and
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/130
---
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 Aldrin,
Appreciate for these details! Really helpful for understanding.
The good feedback is those connections are dashed out immediately after the
internal rows are deleted.
Wish the new design can reduce such confusion.
Cheers,
Bob
Date: Tue, 8 Dec 2015 19:19:16 -0700
From:
+1 (non binding)
On Thursday, 10 December 2015, Ryan Blue wrote:
> +1 (non-binding)
>
> Checked source artifact, spot-checked some license docs on new modules
>
> rb
>
> On 12/08/2015 02:58 PM, Ricky Saltzer wrote:
>
>> +1
>>
>> build works
>> test works
>> hashes/keys check
+1 (non-binding)
Checked source artifact, spot-checked some license docs on new modules
rb
On 12/08/2015 02:58 PM, Ricky Saltzer wrote:
+1
build works
test works
hashes/keys check out
tested a couple simple workflows
On Tue, Dec 8, 2015 at 4:57 PM, Joe Percivall <