[ https://issues.apache.org/jira/browse/TRAFODION-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077348#comment-16077348 ]
ASF GitHub Bot commented on TRAFODION-2628: ------------------------------------------- GitHub user zellerh opened a pull request: https://github.com/apache/incubator-trafodion/pull/1170 [TRAFODION-2628] SQL engine work for Elasticity It turns out that the compiler already kept a list of node ids, not assuming that node ids are consecutively numbered 0...n-1. However, this list was contained in lots of other data structures that are dead code, coming from the time before Trafodion was open-sourced. The change does two things: a) getting rid of obsolete info and b) maintining a list of node ids in the NAClusterInfo class. This change does not include executor modifications. The executor might work just fine, or we may need to add a fix (or optimization) for cases where we pick a node id for a new process at runtime. You can merge this pull request into a Git repository by running: $ git pull https://github.com/zellerh/incubator-trafodion bug/elasticity Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/1170.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1170 ---- commit 4bea445d03b5712007ab326464a8b64b8c2b3740 Author: Hans Zeller <hzel...@apache.org> Date: 2017-07-06T23:11:55Z [TRAFODION-2628] SQL engine work for Elasticity It turns out that the compiler already kept a list of node ids, not assuming that node ids are consecutively numbered 0...n-1. However, this list was contained in lots of other data structures that are dead code, coming from the time before Trafodion was open-sourced. The change does two things: a) getting rid of obsolete info and b) maintining a list of node ids in the NAClusterInfo class. This change does not include executor modifications. The executor might work just fine, or we may need to add a fix (or optimization) for cases where we pick a node id for a new process at runtime. ---- > SQL engine work for Elasticity [TRAFODION-2001] > ----------------------------------------------- > > Key: TRAFODION-2628 > URL: https://issues.apache.org/jira/browse/TRAFODION-2628 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp > Affects Versions: 2.2-incubating > Reporter: Hans Zeller > Assignee: Hans Zeller > Fix For: 2.2-incubating > > > See discussion in TRAFODION-2001. We need to accommodate node ids in a > cluster that contain "holes". -- This message was sent by Atlassian JIRA (v6.4.14#64029)