Github user jtstorck commented on the issue:
https://github.com/apache/nifi/pull/976
+1 on this PR.
Based on the scope of the code changes and the unit testing that has been
introduced, this addresses the use-case of being able query tables based on a
hierarchy of columns that take a primary column and partition columns into
consideration.
I did not run this against a live database, so the committer may want to do
that for a sanity check. The unit tests pass and look like they cover the
hierarchical partitioned query use cases, and they use Derby as the database.
There is one known issue that could occur with partitioning, in that not
all data would be fetched from a partition if new data comes in that provides a
new value for a partition column before all the data in the previous partition
was retrieved. According to @mattyb149, this is an edge case. I think this
issue can be avoided with flow design to account for this, at any rate.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
