[ https://issues.apache.org/jira/browse/ASTERIXDB-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350997#comment-16350997 ]
ASF subversion and git services commented on ASTERIXDB-2232: ------------------------------------------------------------ Commit 2f934e312e841223aa0e4941e01f23b9e63fdc18 in asterixdb's branch refs/heads/master from [~luochen01] [ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=2f934e3 ] [ASTERIXDB-2231][STO] Separate primary op tracker for each partition - user model changes: no - storage format changes: no. - interface changes: yes. Details: - Separate primary index operation tracker for each partition, instead of having a global one on each NC to achieve better scalability. - As a coordinated change, separate component id generator for each partition as well. - Add partition to transaction context so that transaction operations can operate on proper op tracker. - Fixes [ASTERIXDB-2232] to calculate dataset partitions correctly. Change-Id: I9eb3854d2343e45beeccb87b0d434e5f4efd69c9 Reviewed-on: https://asterix-gerrit.ics.uci.edu/2263 Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu> Reviewed-by: abdullah alamoudi <bamou...@gmail.com> > The calculation of dataset partitions for commit runtime is incorrect > --------------------------------------------------------------------- > > Key: ASTERIXDB-2232 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-2232 > Project: Apache AsterixDB > Issue Type: Bug > Components: RT - Runtime, TX - Transactions > Reporter: Chen Luo > Assignee: Chen Luo > Priority: Major > > Dataset.getDatasetPartitions method always returns partitions starting from > 0, which is not the actual partition of the dataset. -- This message was sent by Atlassian JIRA (v7.6.3#76005)