[
https://issues.apache.org/jira/browse/PHOENIX-6344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281822#comment-17281822
]
ASF GitHub Bot commented on PHOENIX-6344:
-----------------------------------------
virajjasani commented on pull request #1135:
URL: https://github.com/apache/phoenix/pull/1135#issuecomment-776002281
@swaroopak one question (not exactly related to this PR):
From `getIndexesPTableForCascade()`, we have this block:
```
// a child view has access to its parents indexes,
// this if clause ensures we only get the indexes that
// are only created on the view itself.
if (index.getIndexType().equals(IndexType.LOCAL)
|| (isView &&
index.getTableName().toString().contains("#"))) {
indexesPTable.remove(index);
}
```
Having `#` in indexName represents that it is parent index and not view's
own index? If so, is that the only way to differentiate it as of now or do we
have some attribute?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> CASCADE on ALTER should NOOP when there are no secondary indexes
> ----------------------------------------------------------------
>
> Key: PHOENIX-6344
> URL: https://issues.apache.org/jira/browse/PHOENIX-6344
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Swaroopa Kadam
> Assignee: Swaroopa Kadam
> Priority: Minor
> Fix For: 5.1.0, 4.16.1, 4.17.0
>
>
> When a table/view does not have a secondary index, using cascade in the ALTER
> TABLE/VIEW .. ADD <column> should continue with default behavior (of only
> adding the column to table/view like a regular alter statement)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
