https://github.com/apache/nifi/pull/108
or should I pull it out.
Just to clarify some of the concerns
- This is just a folder in the ‘external’. It’s not a sub-module of NiFi which
means it’s not part of NiFi build and/or distribution.
- While it’s possible to go the route of attaching remote deb
Oleg
How about you keep it in github for now. We can make a page or section on
the website that points to community supported utilities that helps folks
get underway?
Anyone else see it differently?
Thanks
Joe
On Nov 18, 2015 12:53 PM, "Oleg Zhurakousky"
wrote:
> https://github.com/apache/nif
@Joe, that’s what we have now and I am good with it.
Let’s see if anyone else will chip in and if not I’ll pull it back, no need to
linger there
Oleg
> On Nov 18, 2015, at 2:01 PM, Joe Witt wrote:
>
> Oleg
>
> How about you keep it in github for now. We can make a page or section on
> the w
I agree with Joe
On Nov 18, 2015 2:02 PM, "Joe Witt" wrote:
> Oleg
>
> How about you keep it in github for now. We can make a page or section on
> the website that points to community supported utilities that helps folks
> get underway?
>
> Anyone else see it differently?
>
> Thanks
> Joe
> On N
Hi
I am trying to call Nest 'https://' API to get thermostat data, but I am
not sure how to setup 'SSL Context Service'. Any help appreciated.
Satya
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/How-to-get-Nest-data-tp5082.html
Sent from the Apache Ni
I will put something on getting started page.
I agree with Joe
On Nov 18, 2015 2:02 PM, "Joe Witt" wrote:
> Oleg
>
> How about you keep it in github for now. We can make a page or section on
> the website that points to community supported utilities that helps folks
> get underway?
>
> Anyone el
I love when you agree with yourself ;)
> On Nov 18, 2015, at 2:33 PM, Joe Witt wrote:
>
> I will put something on getting started page.
> I agree with Joe
> On Nov 18, 2015 2:02 PM, "Joe Witt" wrote:
>
>> Oleg
>>
>> How about you keep it in github for now. We can make a page or section on
>>
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/108#issuecomment-157839054
After discussing it with the team we agreed (at least for now) simply keep
the reference to my github - https://github.com/olegz/nifi-ide-integration and
it is already refle
Github user olegz closed the pull request at:
https://github.com/apache/nifi/pull/108
---
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 jskora commented on the pull request:
https://github.com/apache/nifi/pull/116#issuecomment-157853063
Ok, I think that commit fixes the validation issue. This commit
1. adds a custom validator checking that the expression is either valid EL
or valid RE, and
2. adds
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/116#issuecomment-157854900
Awesome and thanks! Will put this on the queue to review if @trkurc doesn't
beat me to it.
n.b. The adjustments for guarding the UUID attribute were merged in earlie
Satya,
Not sure on the specifics of interacting with the Nest API endpoints, but
can certainly help you on your way. At minimum, you will need to configure
the truststore for your SSL Context.
There is a thread from the mailing list that goes into greater depth
concerning this in NiFi [1]
Summa
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/116#issuecomment-157877275
@apiri - I'll take this one, I've got unit tests locally. I'll get a patch
up for NIFI-1187 if you have some review cycles.
---
If your project is set up for it, you can
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/116#issuecomment-157877476
Sounds like a plan. Will look for patch.
---
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 doe
Hi Aldrin
Thank you for your response. I want to call below https from NIFI 'GetHttp'
processor. To be able to make a https call I need to setup SSL Context.
What values I need to set in 'SSL Context Service' .
https://api.home.nest.com/oauth2/access_token?client_id=xxx6b2&code=AUTHORIZATION_COD
Satya,
You will need to configure the truststore properties for your SSL Context
Service instance with:
Truststore Filename: the cacerts file from your Java installation
If $JAVA_HOME Is set on your system, it should help point you in the right
direction. If not, the location of cacerts varies
I've reviewing Joseph Percivall's NIFI-1081. It added
org.apache.nifi.processors.standard.util.SoftLimitBoundedBAOS
How do we feel about BAOS vs ByteArrayOutputStream?
Also, it was heavily based on Hadoop's implementation of I believe
org.apache.hadoop.io.BoundedByteArrayOutputStream [1]
The bel
Hey Tony,
Regarding BAOS vs ByteArrayOutputStream, I made it ByteArrayOutputStream
because it a utility class within the standard processors package and not an
inner private class. I figured we don't know for sure if everyone knows what
BAOS is off the top of their head (I didn't at first) so b
+1 for spelling it out. Those acronyms may save one from typing, but introduce
more confusion. With modern IDE long names is no longer a problem.
Sent from my iPhone
> On Nov 18, 2015, at 18:40, Joe Percivall
> wrote:
>
> Hey Tony,
>
> Regarding BAOS vs ByteArrayOutputStream, I made it Byte
Joe,
It looks to me from your patch like you named it BAOS.
From:
https://issues.apache.org/jira/secure/attachment/12773032/NIFI-1081_02.patch
an example:
import org.apache.nifi.processors.standard.util.SoftLimitBoundedBAOS;
On Wed, Nov 18, 2015 at 6:40 PM, Joe Percivall <
joeperciv...@yahoo.c
You're right. I am thinking of the patch I just put up for 1086 where I use the
same util. In that patch I named it ByteArrayOutputStream. I can rename 1081
real quick.
I plan on rebasing either 1081 or 1086 to account for the util but for now I
just put it in both.
[1] https://issues.apache.o
Combing for examples this was one of the only I could find that was similar:
>From Accumulo:
This product includes the following work from the Apache Thrift project:
TNonblockingServerSocket.java
Apache Thrift
Copyright 2006-2010 The Apache Software Foundation.
[1] https://github.com/apache/
I did find:
>From Phoenix (https://github.com/apache/phoenix/blob/master/NOTICE)
It includes software from other Apache Software Foundation projects,
including, but not limited to:
- Apache HBase
- Apache Hadoop
- Apache Commons
>From Mahout (https://github.com/apache/mahout/blob/master/NO
GitHub user rdblue opened a pull request:
https://github.com/apache/nifi/pull/128
NIFI-1193: Add Hive support to Kite storage processor.
This adds a Hive dataset implementation that shades and minimizes the
classes needed to connect to the Hive MetaStore.
You can merge this pull
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/116#issuecomment-157962791
@jskora - this was merged in but I neglected to add the "This closes #116"
to the commit message.
---
If your project is set up for it, you can reply to this email and h
Github user jskora commented on the pull request:
https://github.com/apache/nifi/pull/116#issuecomment-157970085
Do you need me to close the pull request?
---
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 do
26 matches
Mail list logo
