v0.* QueryDatabaseTable vs v1 GenerateTableFetch

2016-08-15 Thread Peter Wicks (pwicks)
What is the future of QueryDatabaseTable? Unless I'm misunderstanding how it works it looks like GenerateTableFetch can do everything QueryDatabaseTable can do and then some. Is there a plan to phase out QueryDatabaseTable? Is there a reason for a new processor instead of an update to QueryDat

RE: v0.* QueryDatabaseTable vs v1 GenerateTableFetch

2016-08-15 Thread Peter Wicks (pwicks)
Oh, disregard :). I misread GenerateTableFetch as being an actual data fetch vs a query builder. From: Peter Wicks (pwicks) Sent: Monday, August 15, 2016 9:11 PM To: 'users@nifi.apache.org' Subject: v0.* QueryDatabaseTable vs v1 GenerateTableFetch What is the future of QueryDat

Re: v0.* QueryDatabaseTable vs v1 GenerateTableFetch

2016-08-15 Thread Matt Burgess
Peter, Another difference between the two (besides the paging) is that QueryDatabaseTable executes SQL and GenerateTableFetch generates SQL. With the paging capability (which with Remote Process Groups enables distributed fetch a la Sqoop), you're likely correct that GTF will replace / deprecat

Re: v0.* QueryDatabaseTable vs v1 GenerateTableFetch

2016-08-15 Thread Matt Burgess
9:11 PM > To: 'users@nifi.apache.org' > Subject: v0.* QueryDatabaseTable vs v1 GenerateTableFetch > > What is the future of QueryDatabaseTable? Unless I’m misunderstanding how it > works it looks like GenerateTableFetch can do everything QueryDatabaseTable > ca