[ https://issues.apache.org/jira/browse/PHOENIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell reopened PHOENIX-374: ------------------------------------ I was trying to compile the 1.4 branch (4.x-HBase-1.4) and got this error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:compile (default-compile) on project phoenix-core: Compilation failure [ERROR] phoenix-core/src/main/java/org/apache/phoenix/schema/PTableImpl.java:[1294,55] cannot find symbol [ERROR] symbol: method putIfAbsent(java.lang.String,java.util.ArrayList<org.apache.phoenix.schema.PColumn>) [ERROR] location: variable colFamToDynamicColumnsMapping of type java.util.Map<java.lang.String,java.util.List<org.apache.phoenix.schema.PColumn>> Reverting this commit fixed the build. > Enable access to dynamic columns in * or cf.* selection > ------------------------------------------------------- > > Key: PHOENIX-374 > URL: https://issues.apache.org/jira/browse/PHOENIX-374 > Project: Phoenix > Issue Type: New Feature > Reporter: nicolas maillard > Assignee: Chinmay Kulkarni > Priority: Critical > Attachments: PHOENIX-374.patch > > Time Spent: 4h > Remaining Estimate: 0h > > As of recent work we can now read and write columns that are not in the > schema, AKA dynamic columns. the Select and Upsert allow dynamic columns to > be specified. > I think two additions are still needed. > - Alter dynamicly: In the Upsert and/or Select statement the ability to add > on the specified dynamic column to schema. Say Upsert into Table (key, > cf.dynColumn varchar SCHEMAADD) values (..) > and for select: > - select key, cf.dynColumn varchar from T would only read > - select key from T(cf.dynColumn varchar ) would only read and wrtie to > schema > - Select a complete column Family: More complex, accessing a whole Column > Family with all rows known in schema or not. > select cf.* from T > today this works for know columns it could be nice to have this for all > columns of a family in the schema or not. I'm trying right now to extend this > to schema for unknown columns. However every new row can a lot of very > different unknowcolumns. The defined ones will be first but the unknown one > will be appended at the end. > This means the metadata might need to be updated at every row to account for > all new columns discovered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)