If you haven't heard yet, the Apache Software Foundation was selected
as an organization for this year's Google Summer of Code [1]. I've
seen activity on other Apache projects' mailing lists requesting ideas
for issues, features, components, etc. that could be good
proposals/ideas for GSoC, and I'd
Looking at the code, it appears that PutFile should support the
creation of arbitrary directories if the Create Missing Directories
property is set to true. With that and setting the Directory property
to ${path}, I would think that would create the subdirectories
properly. If not, what error are y
[1] http://s.apache.org/gsoc2018ideas
On Wed, Feb 28, 2018 at 12:12 AM, Joe Witt wrote:
> Matt
>
> Did you have some ideas/features/enhancements in mind you think would
> be good to propose?
>
> Thanks
> Joe
>
> On Tue, Feb 27, 2018 at 6:56 PM, Matt Burgess wrote:
>>
Milan,
Unfortunately no, without code changes the Hive processors are not
compatible with Hive 1.1.x. There were API changes both to the Java code
and the Thrift code (the latter adds the client_protocol field you
mentioned), so you can't change the version of the Hive dependencies and
get the NA
The Atlas profile is intentionally not included in the default assembly, I
believe due to its size.
Sent from my iPhone
> On Mar 10, 2018, at 10:03 AM, Pierre Villard
> wrote:
>
> Hi Mike,
>
> I see where the problem is. It's been introduced with NIFI-4936.
> I also noticed that the atlas pr
+1
On Sun, Mar 11, 2018 at 1:00 PM, Jeff wrote:
> +1
>
> On Sat, Mar 10, 2018 at 8:42 PM Joe Skora wrote:
>
>> +1
>>
>>
>> On Fri, Mar 9, 2018, 3:10 PM Scott Aslan wrote:
>>
>> > All,
>> >
>> > Following a solid discussion for the past couple of weeks [1] regarding
>> the
>> > establishment of
Rohit,
Are you routing both the "split" and "original" relationships to the
downstream processor? If so, and you don't want the 6th flowfile
containing all 5 records, then do not route the original relationship
to the downstream processor. You can route it to some other processor
or self-terminate
Milan,
You could subclass the existing HiveConnectionPool, add a property for
key/truststore password that is sensitive, then build the URL manually
during a call to getConnection(). Then the rest of the URL would not
have to remain sensitive, if that is preferable. You might even
consider an SSL
Rohit,
Do you mean the SelectHiveQL processor? If so can you share more
information about your configuration, the query, the table, etc.? If
you are using a custom processor, can you share its location? Perhaps
the author or other users of it can address this.
Thanks,
Matt
On Wed, Mar 14, 2018
Rohit,
Hive is not supported by the database fetch processors yet, there is a
Jira [1] and some PRs [2],[3] under review to add this capability.
Regards,
Matt
[1] https://issues.apache.org/jira/browse/NIFI-3093
[2] https://github.com/apache/nifi/pull/1281
[3] https://github.com/apache/nifi/pull/
I think Bryan is asking about what happens AFTER this part of the
flow. For example, if you are doing routing you can use QueryRecord
(and you won't need the SplitJson), if you are doing transformations
you can use JoltTransformJSON (often without SplitJson as well), etc.
Regards,
Matt
On Tue, Ma
gt;> >> From there on we use a lot of routeOnAttritutes and use that values on
>> sql queries to other tables like select * from someTable where
>> id=${myExtractedAttribute}
>> >> To be honest I tryed JoltTransformJSON but I could not get it working :)
>> >>
>
This sounds like a bug in HiveJdbcCommon, we should be able to support
a Hive SMALLINT into an Avro integer or something.
On Tue, Mar 20, 2018 at 11:53 AM, Rohit wrote:
> Hi Matt,
>
> Issue got resolved after casting smallint to int, as avro not supported
> smallint datatype.
>
> Thanks.
>
>
>
>
Bri/yan,
IMO I think we'd be better off with moving the
nifi-mongodb-client-service-api and nifi-mongodb-services bundles into
the nifi-mongodb-bundle. That's something I missed while reviewing the
PR that put them in standard services. I don't see a direct dependency
on nifi-standard-services, an
stry will be a powerful capability.
>
> Also, +2 for the greeting, though Bryan may choose to put the "y" first. :-)
>
> Thanks,
> Brian
>
> On Mon, Mar 26, 2018 at 5:13 PM Matt Burgess wrote:
>
>> Bri/yan,
>>
>> IMO I think we'd be better
+1 (binding) Release this package as nifi-1.6.0
Verified checksums, commit, L&N, etc. Ran full build with unit tests
and tried various flows, all looks well!
On Mon, Mar 26, 2018 at 11:34 PM, Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> Ni
+1 (binding), ran through the verification helper on Mac OS X 10.13.4
with full build, tried various flows and validated a couple fixes.
Thanks for handling the release Joe!
On Tue, Apr 3, 2018 at 7:49 PM, Joe Witt wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release o
Mike,
Is there a workaround for this? Like setting the query key(s) for
insert even if they are ignored? Or will that cause other issues?
Thanks,
Matt
On Fri, Apr 6, 2018 at 8:56 AM, Mike Thomsen wrote:
> Sorry to be the bearer of bad news, but this morning I found a bug in
> PutMongo that bre
+1 to Andy's answer. Note that DBCPConnectionPool isn't a connection
but a connection pool, which keeps some number of connections
available for use by multiple consumers (processors, e.g.). I wouldn't
want to have to keep track of X number of configurations in a single
controller service, which wo
I’m AFK right now but I’m thinking there is a point in the lifecycle where you
can expect a logger, and before that (like when the processor is instantiated
as you have it coded), you may not be able to assume there is a logger (either
in real NiFi or the mock-verse :)
My guess is the rule of t
If that's the case, you may be able to fix that by adding the
following property to your hdfs-site.xml:
dfs.client.use.datanode.hostname = true
It should cause the hostnames of the data nodes to be returned to the
client, rather than private/inaccessible IPs.
Regards,
Matt
On Thu, Apr 19, 2018
You may also need to add a NAR dependency to your processor's NAR's
POM if you haven't already:
org.apache.nifi
nifi-standard-services-api-nar
1.7.0-SNAPSHOT
nar
On Thu, Apr 19, 2018 at 12:08 PM, rishabprasad005
wrote:
> Yes, I have added nifi-dbcpservice-api in processor pom
Max,
ExecuteGroovyScript does not (yet) automatically include some Apache
Commons libraries such as commons-lang3, commons-io, commons-net, etc.
However ExecuteScript does already include those, so you can put your
Groovy script in there and not have to @Grab the library. Of course,
you won't get
All,
As Joe implied, I'm very happy that we are discussing graph tech in
relation to NiFi! NiFi and Graph theory/tech/analytics are passions of
mine. Mike, the examples you list are great, I would add Titan (and
its fork Janusgraph as Kay-Uwe mentioned) and Azure CosmosDB (these
and others are at
IMO the concept of "functions" is different enough to warrant its own
set of components, rather than trying to shoehorn them into a wormhole
/ PG discussion. Perhaps a Function component which may feel like a PG
(but with UI distinction such as rounded corners?), but would be
referred to by name (u
Makes sense to me, I'm a +1 as well.
On Wed, May 16, 2018 at 4:52 PM, Scott Aslan wrote:
> Good timing as we're close to ready for a first nifi-fds release.
>
> I would definitely favor us keeping the 'nifi-fds' naming as that means I
> dont have to change a bunch of code so Apache NiFi Flow Desi
+1 (binding)
On Fri, May 18, 2018 at 10:26 AM, Bryan Bende wrote:
> +1 (binding)
>
> On Fri, May 18, 2018 at 10:18 AM, James Wing wrote:
>> +1 (binding)
>>
>>> On May 18, 2018, at 6:30 AM, Rob Moran wrote:
>>>
>>> Following positive response discussing the name change of nifi-fds [1], I'd
>>> l
You can use a SiteToSiteBulletinReportingTask [1], it will send flow
files containing bulletins to an Input Port on the root process group
(aka top-level canvas), then you can send to whichever processors you
like for further operations.
Regards,
Matt
[1]
https://nifi.apache.org/docs/nifi-docs/c
Mike,
IIRC the "top-level" EL evaluator will go through a string finding EL
constructs and pass them into Query I think. Also ReplaceText (for
some reason) is the only place I know of where you can quote something
and (if EL is present), the result is treated as a string literal.
Otherwise in NiF
Congratulations and welcome aboard Sivaprasanna!
On Tue, Jun 5, 2018 at 10:09 AM, Tony Kurc wrote:
> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Sivaprasanna has accepted the PMC's invitation to become a committer on the
> Apache NiFi project. We greatly appreciate all
Anil,
Are you using SplitRecord because something times out in
PutDatabaseRecord otherwise? If not, you shouldn't need the
SplitRecord, and without it, things should work the way you expect.
If you do need to split into smaller flow files, you should be able to
use Wait/Notify with the parent flo
Congratulations Mike! Great to have you aboard, I appreciate your
commitment and work ethic and looking forward to continued great
things!
On Wed, Jun 6, 2018 at 6:22 PM, Tony Kurc wrote:
> NiFi community,
> On behalf of the Apache NiFi PMC, I am pleased to announce that Mike
> Thomsen has accep
essSession.read resulting in outer stream
> > being
> > > >>> closed — Mark Payne
> > > >>> * NIFI-5209 Remove toolkit migration without password functionality —
> > > Andy
> > > >>> LoPresto
> > > >>> * NIFI-5166 C
I think is a great idea, I filed a Jira [1] a while ago in case
someone wanted to start working on it (or in case I got a chance). It
mentions ARX but any Apache-friendly implementation is of course
welcome. I think it should be in its own bundle as it is functionality
separate from all our other b
+1 (binding)
Verified all artifacts, full build with contrib-check, verified the
Hive 3 NAR is not in the assembly unless the include-hive3 profile is
activated, also ran through various flows to exercise Hive 3 and
PutORC functionality (and their associated Record Readers, Writers,
and intermedia
> '${project.basedir}'.
>
> Thanks.
>
> On Wed, Jun 20, 2018 at 11:15 PM, Matt Burgess wrote:
>
> > +1 (binding)
> >
> > Verified all artifacts, full build with contrib-check, verified the
> > Hive 3 NAR is not in the assembly unless the i
Do your processors work against 1.6.0? I’m wondering if there’s something with
the new Expression Language scope stuff, I believe that can cause unit test
failures even if it still works (albeit deprecated) on a live NiFi.
Regards,
Matt
> On Jul 2, 2018, at 4:52 PM, Mark Payne wrote:
>
> Hey
I would say it’s “expected”, properties with allowable values shouldn’t support
EL per se, although there are properties in NiFi where one of the allowable
values is “Use x.y.z attribute” which implies Flow File scope but isn’t
documented via annotations or anything but the description.
Regards
This Jira search [1] for Bugs resolved in 1.8.0 has 10 items, there
are some I don't see in this list (NIFI-5278 [2] and NIFI-5349 [3]),
should these all be included or on a case-by-case basis?
Thanks,
Matt
[1]
https://issues.apache.org/jira/browse/NIFI-5394?jql=project%20%3D%20NIFI%20AND%20fixV
Netflix uses Atlas [1], the standalone JAR is only 8 KB [2] but it's
written in Scala, not sure what the overall footprint of the Scala
libraries and other dependencies are...
Regards,
Matt
[1] https://github.com/netflix/atlas/wiki
[2] https://mvnrepository.com/artifact/com.netflix.atlas/atlas-st
Looks like they've identified the onus being on the client not the
library. We do read column types when a Distributed Map Cache Client
is specified, so we should probably be able to do these conversions.
Please feel free to write a Jira [1] to cover this.
Thanks,
Matt
[1] https://issues.apache.o
Joe,
Thanks for bringing this to our attention, definitely something to
keep aware of. I did some initial digging, it appears that the
"normal" Redis stuff is still Apache 2.0 licensed, and it appears that
will remain; also AFAICT we are only using the "normal" Redis bits via
spring-data-redis, bu
ExecuteSQL outputs Avro with an embedded schema, it is the Avro schema
that doesn't allow parentheses in the field names. You can avoid the
error by setting Normalize names to true as you found, and also you
could alias the field names in the SQL itself, such as:
SELECT RANGE(flowenddate) AS flowE
Christophe,
IIRC the isNullable() method gives inconsistent results across JDBC
drivers (see [1], [2] for examples) and in such cases might cause more
harm than good. Having said that, we could perhaps add a property to
the relevant components such as "Honor Non-Nullable Fields" or
something like
I think the general capability you are referring to is called
"dependent properties" and it has not yet been implemented [1]. To
some extent you can do this programmatically by overriding
customValidate() or onPropertyModified() for example, and updating the
list of PropertyDescriptors that are re
Moving users list to BCC and adding devs list, as this question is
better suited for the devs.
Ed,
Does XMLReader not parse your XML? I guess you'd need to know the
schema so if you don't (especially if it is dynamic) then you might be
faced with a custom processor as you described.
Take a look
Maxime,
I believe this is a bug, specifically at [1]. It should support
MapRecord entries as well. I have written NIFI-5678 [2] to address
this. The workaround is the one you and Bryan mentioned, using a
record instead of a map.
Regards,
Matt
[1]
https://github.com/apache/nifi/blob/master/nifi-
ertex with label "Token" and attribute "name"="Mary"). If the
>>>>> vertex does not exist, the vertex has to be created.
>>>>> Since I want to save e.g. Wikipedia to my graph I want to avoid the
>>>>> supernode problem for t
+1 (binding), verified via release helper, ran full build with unit
tests, tried various flows on a standalone instance. Great work
everyone! Thanks Jeff for RM'ing!
On Wed, Oct 17, 2018 at 11:59 PM Jeff wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache N
I’m not at my computer but I think your ControllerService file (for
ServiceLoader) might need to be in META-INF/services instead of
META-INF.services?
Sent from my iPhone
> On Oct 21, 2018, at 1:56 PM, Sivaprasanna wrote:
>
> Team,
>
> I'm working on a controller service implementation (NIFI
+1 (binding), ran through release helper, tested various flows
including record-based processors and Hive 3 processors (although the
Hive 3 NAR is not in the assembly).
On Tue, Oct 23, 2018 at 1:56 AM Jeff wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
I think you're running into NIFI-5525 [1], it should be fixed in master as
well as the upcoming 1.8.0 release.
Regards,
Matt
[1] https://issues.apache.org/jira/browse/NIFI-5525
On Wed, Oct 24, 2018 at 7:14 AM Nalinrat Laekawan
wrote:
> Hi nifi team,
>
> I found some issue with CSVreader in NI
NiFi (as of the last couple releases I think) has the ability to set
auto-terminating relationships; this IMO is one of those use cases
(for NiFi 1.x). If new relationships are added, they could default to
auto-terminate; then the existing processors should remain valid.
However we might want an "o
I do not think most users
> would appreciate it being a condition silently not handled by the normal
> failure path.
>
> Thanks,
> Peter
>
> -Original Message-
> From: Matt Burgess [mailto:mattyb...@apache.org]
> Sent: Friday, October 26, 2018 10:18 AM
>
Ulisses,
There is a Jira [1] along with a patch [2] to add this feature, but it
appears to have languished for most of the year. I will leave a
comment on the PR to see if the author is interested in continuing the
work; otherwise, perhaps someone else from the community will pick it
up.
Regards,
Dave,
Depending on the processor you're going to use to store these records
into cache (see Mike's reply), if you want to convert each of the
lines to JSON objects, you can use ReplaceText:
Search Value: ^([^:]+):(.*)
Replacement Value: {"$1":$2}
Replacement Strategy: Line By Line
This creates a
Ryan,
I'm glad to join my NiFi community colleagues by saying "welcome
aboard!!" and we'll do our best to get you up and running :) For the
Jira part, Apache's Jira lets you create a case without being a
contributor for that particular project. For that reason, there are a
few NIFI cases out there
Alex,
Your interest in contributing is most welcome, thanks in advance!
What is your Apache Jira username? I should be able to take care of
this for you.
Regards,
Matt
On Wed, Jan 30, 2019 at 4:59 PM Alex Aversa wrote:
>
> Hello,
>
> I had created a ticket in JIRA and it appears I am unable to
.
> > > >
> > > > On Thu, Feb 7, 2019 at 1:17 AM Andy LoPresto
> > > wrote:
> > > >
> > > > > Ah, sorry, I misunderstood. You are not the PR author; you want those
> > > > same
> > > > > comments to be addressed.
>
+1 (binding) Release this package as nifi-1.9.0
Ran through release helper, tried various flows using several
components, everything looks good.
Thanks Joe for RM'ing!
On Sat, Feb 16, 2019 at 10:50 PM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of
+1 to Bryan's comments. If I had to guess I'd say the error is
probably in the line:
kuduTable = clientService.getKuduClient().openTable(tableName);
That's the only one that does heavy lifting vs standard NiFi API
calls, and should be in a try/catch for that reason. Also IIRC setting
up external
Kevin,
I feel your pain, that's a particularly nasty bug, and in fact there
were a few bugs to be included in the 2.7.2 release. However, AFAIK
Jython 2.7.2 was never released. The latest in Maven is 2.7.1 [1], and
even in Github there's only a 2.7.2 alpha tag [2]. Do you know of a
place to get a
+1 (binding) Release this package as nifi-1.9.1
Ran the release helper and various flows including one exercising one
of the changes in this release.
On Wed, Mar 13, 2019 at 1:49 AM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.9.1.
Franklin,
What kind of support do you mean? Maybe an "official" NiFi Gradle
plugin to build NARs, like the NAR MOJO plugin for Maven? What are the
concerns with using the third-party library (I heard it works fine)? I
also wrote my own inline script [1] (rather than a plugin) you could
use in your
+1 (binding) Release this package as nifi-nar-maven-plugin-1.3.0
Ran through release helper, verified artifacts. Thanks for RM'ing Bryan!
On Tue, Apr 30, 2019 at 12:03 PM Bryan Bende wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi NAR Maven Plug
Mike,
Check AbstractRouteRecord, it uses the read-first-get-schema-read-rest
pattern. However for that snippet, it is the RecordReader that is
possibly updating the schema (currently the only thing that does this
is schema inference), then the RecordSetWriter is created using the
(possibly updated
multiple schema levels that don't exist. How should that be handled? An
> exception or generating empty record declarations that have one field?
>
> On Tue, May 21, 2019 at 2:07 PM Matt Burgess wrote:
>
> > Mike,
> >
> > Check AbstractRouteRecord, it uses the read-fi
Try this spec:
[
{
"operation": "shift",
"spec": {
"somedate": "somedate.\\$date"
}
}
]
I haven't tried this in NiFi (only in http://jolt-demo.appspot.com),
if there's an issue with Expression Language you might need to escape
more of the $ somehow.
Regards,
Matt
On Fri, M
Mike,
I definitely like the idea. If the list is long we could create an
Epic case and people can keep biting off chunks of it into Jira cases
underneath. Or if they're easily categorizable (like extending your
recent PR [1] into all scriptable components), we could have a Jira
for each "area", as
Mike,
I’ll review those two graph PRs tonight or tomorrow (if they’re still open by
then)
> On Aug 29, 2019, at 3:43 PM, Mike Thomsen wrote:
>
> I have two open graph-related PR's that are really small and are needed to
> close some bugs that will be bad for early adopters:
>
> https://github
Andrew,
Welcome! I have added you as a Contributor to all the NiFi projects.
Looking forward to your contributions!
Regards,
Matt
On Wed, Oct 16, 2019 at 11:31 AM Andrew Rodriguez
wrote:
>
> Hello,
>
> I was hoping to gain access to contribute, as I'm able. My Jira username is
> atrodriguez.
>
Congratulations Peter!
On Sun, Oct 27, 2019 at 9:05 PM Aldrin Piri wrote:
>
> Apache NiFi community,
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that Peter
> has accepted the PMC's invitation to become a committer on the Apache NiFi
> project. We greatly appreciate all of
+1 (binding)
Ran thru the release helper and tried a number of flows with various
controller services and processors, LGTM
Thanks for RM'ing Joe!
On Tue, Oct 29, 2019 at 1:32 PM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.10
Nissim,
I have added you as a contributor on the 3 NiFi projects in Jira.
Looking forward to your contributions!
Regards,
Matt
On Tue, Nov 12, 2019 at 12:29 PM Nissim Shiman
wrote:
>
> Hello Apache Nifi team,
> I would like to request jira contributer access to apache nifi. I would like
> to
Shawn,
There are also Redis and Couchbase distributed map cache clients
already in NiFi. I don't see any Jiras or PRs related to a DynamoDB or
JDBC ones. I thought about making ones for JDBC, Hazelcast and/or
Nitrite [1] (with or without a DataGate server), but never got around
to it. I think Dyna
Roger,
I have added you as a Contributor to the NIFI, NIFIREG, and NIFILIBS
projects in Jira, looking forward to your contributions! I'm
interested to know what you have in mind for native Vertica support vs
the RDBMS processors using the Vertica JDBC driver, are you thinking
bulk loading capabili
Alex,
This same thing happened to me a day or two ago. I'm not sure if it's
a bug or works as intended, but the problem stems from trying to
generate doc for an interface that extends ControllerService rather
than a class implementation of ControllerService. I believe it has
something to do with b
Juan,
I have added you as a Contributor to the 3 NiFi Jira projects, looking
forward to your contributions!
Regards,
Matt
On Mon, Dec 16, 2019 at 9:54 PM Juan Sequeiros wrote:
>
> Hello all,
>
> I am requesting "Jira contributor access" and my username is
> digitalplumber.
>
> Thanks
> --
> Ju
Daniel,
I have added you to the 3 NiFi projects in Apache Jira as a
Contributor, looking forward to your contributions!
Regards,
Matt
On Sat, Dec 14, 2019 at 3:51 PM Daniel Magyar
wrote:
>
> Hi,
>
> I'd love to start contributing to Nifi, could you please grant
> me contributor access on the ji
Looks good to me, thanks for putting this together Joe!
On Tue, Jan 7, 2020 at 1:32 PM Joe Witt wrote:
>
> Team,
>
> Here is the content of the board report I submitted for us this quarter.
> Again great progress!
>
> Thanks
> Joe
>
>
> ## Description:
> The mission of NiFi is the creation and ma
Mark,
Good timing; Shawn, Bryan and I were talking about that on the Apache
NiFi Slack just today. It's been captured in NIFI-6852 [1] and Shawn
has drafted a PR [2] and is working on a unit test for it. My overall
thought is that you really shouldn't be binding to the generic
ControllerService, r
Richie,
I have added you as a Contributor to the three NiFi projects in Jira.
Welcome, looking forward to your contributions!
Regards,
Matt
On Wed, Jan 15, 2020 at 11:34 AM Richie Howell
wrote:
>
> Hi all,
> I'd like to request Jira contributor access, my username is rhowell
>
> Thanks,
> Richi
Erik,
It's been fixed in Hive 3, and even though the Hive 3 components don't
come with the distribution of Apache NiFi (due to size concerns), they
can be added manually from the Apache repository [1] [2]. The issue
was fixed in Hive 2 but NiFi does not have a Hive 2 bundle, so if you
are running
+1 (binding)
Ran through release helper, tried various flows including some new
features (PutRecord, e.g.) PutRecord might not have made the
improvements list, changelog, release notes, etc. for 1.11 due to an
omission in Jira, but the Jira has since been corrected [1]
-Matt
[1] https://issues.a
This is a friendly reminder that if you have PRs/patches open against
SNAPSHOT components (or perhaps adding your own) that you should
update the versions to 1.12.0-SNAPSHOT and re-submit, this will help
expedite the review/merge process, please and thanks!
Xun,
I have added you as a contributor to the NiFi projects in Jira.
Welcome! Looking forward to your contributions.
Regards,
Matt
On Tue, Feb 4, 2020 at 7:13 AM Xun REN wrote:
>
> Hello,
>
> Could you please give me the Jira contributor access for NiFi ?
>
> My Jira username is: renxunsaky
>
>
Bence,
I have added you as a contributor to the NiFi projects in Jira.
Welcome aboard, looking forward to your contributions!
Regards,
Matt
On Mon, Feb 10, 2020 at 11:45 AM Bence Simon wrote:
>
> Dear NiFi devs,
>
> I would like to ask you to grant me contributor access. My username is
> simonb
Shawn,
We've done this ad hoc in other places when it made sense to do so.
Maybe we'd want to avoid adding any record values to the error
message, although since the attribute is associated with the flow file
content I'm not sure that's necessary from a security perspective. The
only other thing I
Can you share your configuration for QueryDatabaseTable? Is the
"Database type" property set to the right version of Oracle? Also I
believe you'll need the table name to be capitalized.
Regards,
Matt
On Thu, Feb 13, 2020 at 10:20 AM aboubakry wane
wrote:
>
> Hello,I use nifi to collect data from
+1 (binding) ran through release helper and various flows. Thanks Joe
for RM'ing!
On Fri, Feb 14, 2020 at 10:15 PM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.11.2.
>
> The source zip, including signatures, digests, etc. can be fou
+1 (binding), ran through release helper and verified the file leaks
are fixed for DistributedMapCacheClientService and the SiteToSite
Reporting Tasks. Thanks for RM'ing Joe!
On Fri, Feb 21, 2020 at 10:21 PM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source releas
What about an in-memory (perhaps with disk persistence) representation
of the flow as a graph using Apache Tinkerpop? That would alleviate
the need for a separate graph DB while still allowing you to do graph
searches, at the cost of more memory usage. Not sure what the
footprint would look like fo
Aya,
The Hive components included with Apache NiFi are not compatible with
Hive 2.x, they are built with Hive 1.2.x. There is a Jira to add Hive
2 support [1] but it is not yet in NiFi.
Regards,
Matt
[1] https://issues.apache.org/jira/browse/NIFI-6456
On Tue, Mar 3, 2020 at 6:35 AM Aya Asfour
+1 (binding), ran through release helper and tried various flows
(verifying some of the changes in this release).
Thanks for RM'ing Joe!
On Wed, Mar 18, 2020 at 1:16 PM Joe Witt wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.11.4.
>
> The sou
Looking at the Jiras that were released between 1.8.1 (our current
version) and 1.9.2 (the current GA version of Avro) [1], it appears
that if we were to upgrade Avro, we definitely should go to the latest
(there are a number of regressions in 1.8.2 and 1.9.0 for example).
However I'm a little leer
age of the ObjectMapper class to what it is in Databind 2.x. I
can't find any other reference to the old Databind (or its
ObjectMapper) yet, but still on the case :)
On Tue, Mar 24, 2020 at 1:25 PM Matt Burgess wrote:
>
> Looking at the Jiras that were released between 1.8.1 (our current
>
w the JSON nodes are referenced. I cannot
> remember what the exact issue was, but it wasn't a quick drop and replace
> with maybe a handful of edits.
>
> Maybe I was looking at the wrong thing though...
>
> On Tue, Mar 24, 2020 at 1:26 PM Matt Burgess wrote:
>
> > Looki
Cody,
ExecuteSQL outputs data in Avro format and embeds the schema in the
content of the flow file (which Avro supports), leading to a non-zero
flowfile size. As of NiFi 1.8.0, you can instead use ExecuteSQLRecord
to output the data in any supported format (via a RecordSetWriter
controller service
+1 (binding)
Ran through release helper, verified artifacts, ran through Drew's
"Getting Started With Apache NiFi Registry" tutorial (which is great
btw) to connect NiFi to the Registry and run a few scenarios.
Thanks for RM'ing Arpad!
On Thu, Apr 2, 2020 at 11:54 AM Arpad Boda wrote:
>
> Hello
One thing that was mentioned was an included Jira for "providing a clearer
distinction between framework and
extensions," This involved moving extensions to a new module and for
community folks this is causing problems with any
new improvements in-flight before that. Seems like it needed more
anno
1 - 100 of 594 matches
Mail list logo
