You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@apex.apache.org by "Chandni Singh (JIRA)" <ji...@apache.org> on 2016/08/04 03:37:20 UTC

[jira] [Updated] (APEXMALHAR-722) Investigate re-partitioning of transactional database output adaptor

     [ https://issues.apache.org/jira/browse/APEXMALHAR-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chandni Singh updated APEXMALHAR-722:
-------------------------------------
    Assignee:     (was: Chandni Singh)

> Investigate re-partitioning of transactional database output adaptor
> --------------------------------------------------------------------
>
>                 Key: APEXMALHAR-722
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-722
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>          Components: adapters database
>            Reporter: Chandni Singh
>
> Currently the transactional database output adaptors use operator id to persist last committed window. With this approach the operators cannot be re-partitioned. 
> We need to find a way to make these operators dynamically partition-able.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)