[
https://issues.apache.org/jira/browse/APEXMALHAR-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise updated APEXMALHAR-2514:
-------------------------------------
Description:
Operator currently cannot handle tables where old data is periodically removed,
because the poll logic assumes a fixed start offset. Instead, it should support
offset rebase with a trailing lower bound key.
Such use of the WHERE clause will also avoid repeated full index scanning and
be especially efficient when the source is partitioned on the key column.
https://lists.apache.org/thread.html/50ae7799199ab8b9e38b7947dbcfd466b60df0bbfea6aa19abfd0b33@%3Cusers.apex.apache.org%3E
was:
Operator should take advantage of WHERE clause to avoid repeated full index
scanning.
https://lists.apache.org/thread.html/50ae7799199ab8b9e38b7947dbcfd466b60df0bbfea6aa19abfd0b33@%3Cusers.apex.apache.org%3E
> JDBCPollInputOperator support for purging
> -----------------------------------------
>
> Key: APEXMALHAR-2514
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2514
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Thomas Weise
>
> Operator currently cannot handle tables where old data is periodically
> removed, because the poll logic assumes a fixed start offset. Instead, it
> should support offset rebase with a trailing lower bound key.
> Such use of the WHERE clause will also avoid repeated full index scanning and
> be especially efficient when the source is partitioned on the key column.
> https://lists.apache.org/thread.html/50ae7799199ab8b9e38b7947dbcfd466b60df0bbfea6aa19abfd0b33@%3Cusers.apex.apache.org%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
