nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Thomsen <mikerthom...@gmail.com>
Subject Re: LookupService + flowfile attributes
Date Sat, 09 Jun 2018 12:44:15 GMT
https://issues.apache.org/jira/browse/NIFI-5287

On Sat, Jun 9, 2018 at 1:20 AM Koji Kawamura <ijokarumawak@gmail.com> wrote:

> Thanks Mike for starting the discussion.
>
> Yes, I believe that will make LookupService and Schema access strategy
> much easier, reusable, and useful.
>
> What I was imagined is not adding new method signature, but simply
> copy certain FlowFile attributes into the coordinates map.
> We can add that at LookupRecord.
> Currently LookupAttribute only uses one coordinate value and can be
> left as it is.
>
> Specifically, by adding new processor property, 'Copy FlowFile
> Attributes into Coordinates', where user can define RegularExpression
> to select which attributes to copy.
> I think it's fine to mix FlowFile attributes and values defined as
> dynamic properties into the same coordinates map.
> The put oder should be FlowFile attributes, then dynamic properties,
> so that user can overwrite attribute values when necessary.
>
> Koji
>
>
> On Sat, Jun 9, 2018 at 1:06 AM, Mike Thomsen <mikerthomsen@gmail.com>
> wrote:
> > On the RestLookupService PR I think Koji mentioned the idea of expanding
> > the lookup capability to include flowfile attributes. That sort of thing
> > would be immensely useful on two PRs I have already open for lookup
> service
> > changes for ES and Mongo. Koji, add your thoughts, but what I'm thinking
> > would be a new PR that adds:
> >
> > T lookup(Map<String, String> flowfileAttributes, Map<String, Object>
> > coordinates);
> >
> > to the LookupService interface and has the related processors pass in the
> > flowfile attribute map. Specifically, it would help make the schema
> access
> > capabilities really usable with lookup services (see MongoDBLookupService
> > PR for example; I added a new SchemaRegistryService type for JSON
> sources)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message