[
https://issues.apache.org/jira/browse/PHOENIX-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238547#comment-16238547
]
James Taylor commented on PHOENIX-3837:
---------------------------------------
Some guidance on how to implement this:
- add the {{| (SET (p=fam_properties)) )}} to the {{ALTER INDEX}} grammar rule
in PhoenixSQL.g
- store the property info in the AlterIndexStatement
- call through to MetaDataClient.addColumn() if the set property information is
there. I suspect the code will do the right thing as-is.
[~aertoria] - it is possible to workaround the issue sometimes, but we'd like a
way to set properties in general on indexes.
> Unable to set property on an index with Alter statement
> -------------------------------------------------------
>
> Key: PHOENIX-3837
> URL: https://issues.apache.org/jira/browse/PHOENIX-3837
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.10.0
> Reporter: Mujtaba Chohan
> Assignee: Ethan Wang
> Priority: Major
> Fix For: 4.14.0
>
>
> {{ALTER INDEX IDX_T ON T SET GUIDE_POSTS_WIDTH=1}}
> {noformat}
> Error: ERROR 601 (42P00): Syntax error. Encountered "SET" at line 1, column
> 102. (state=42P00,code=601)
> org.apache.phoenix.exception.PhoenixParserException: ERROR 601 (42P00):
> Syntax error. Encountered "SET" at line 1, column 102.
> at
> org.apache.phoenix.exception.PhoenixParserException.newException(PhoenixParserException.java:33)
> at org.apache.phoenix.parse.SQLParser.parseStatement(SQLParser.java:111)
> at
> org.apache.phoenix.jdbc.PhoenixStatement$PhoenixStatementParser.parseStatement(PhoenixStatement.java:1299)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
