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 / deprecate QDB.
Adding paging to QDB would not have given real distributed fetch, as multiple tasks of QDB would not be able to get the correct pages since they each execute the same code in parallel. GTF is designed to be run on the primary node only, but would be connected (likely via RPG) to ExecuteSQL which can be run in parallel. Regards, Matt > On Aug 15, 2016, at 11:10 PM, Peter Wicks (pwicks) <pwi...@micron.com> wrote: > > 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 > QueryDatabaseTable? It looked like the only user facing change was result > paging, which could have had a default of 0 (no paging). Just curious. > > Regards, > Peter
