RE: [EXT] Calcite version used in Nifi 1.7+

[Ruurd Schoonheim]

Thnx Peter!

Then, somehow CROSS APPLY should work in Nifi 1.7.x+... 樂
On 16 Oct 2018, 15:38 +0200, Peter Wicks (pwicks) , wrote:
> In NiFi 1.7.0 it was Calcite v1.12.0. In NiFi 1.8 it will be Calcite v1.17.0
>
> -Original Message-
> From: ruurd.schoonh...@dbiq.nl [mailto:ruurd.schoonh...@dbiq.nl]
> Sent: Tuesday, October 16, 2018 6:58 AM
> To: dev@nifi.apache.org
> Subject: [EXT] Calcite version used in Nifi 1.7+
>
> Hi guys,
>
> Which version of calcite is used by QueryRecord processor in Nifi 1.7 or 
> above?
>
> I’m looking for CROSS APPLY suport in my query as introduced in Calcite 1.11 
> (january 2017)
>
> Or has anyone a solution to perform select on self joined dataset (recursive)
>
> Kind regards
> Ruurd Schoonheim

Calcite version used in Nifi 1.7+

[ruurd . schoonheim]

Hi guys,

Which version of calcite is used by QueryRecord processor in Nifi 1.7 or above?

I’m looking for CROSS APPLY suport in my query as introduced in Calcite 1.11 
(january 2017)

Or has anyone a solution to perform select on self joined dataset (recursive)

Kind regards
Ruurd Schoonheim

Re: The mystery of ListSFTP that stops working

[ruurd . schoonheim]

Same behavior seen with putHbase processor. 
Nifi restart was only fix. 
Would like to see root cause and way to get control of processor without 
nifi-restart. 


> Op 15 nov. 2017 om 10:58 heeft Andre  het volgende 
> geschreven:
> 
> Folks,
> 
> Has anyone ever seen a situation where ListSFTP simply stops working?
> 
> I have observed a few occurrences of seems to be some weird bug.
> 
> Symptoms are:
> 
> - Processor looks healthy (i.e. no bulletins)
> - State is stalled (i.e. no changes to new files or timestamps)
> - No signs of a stuck thread (i.e. processor doesn't display a thread count)
> - UI displays processor "Task count = 0/0"
> - Neither stopping > starting nor stopping > disabling > enabling >
> starting processor seems to make a difference.
> 
> Has anyone seen this?
> 
> Cheers