[
https://issues.apache.org/jira/browse/PHOENIX-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259498#comment-14259498
]
James Taylor commented on PHOENIX-514:
--------------------------------------
Technically, that would work for serialization, but I'd be worried that we'd be
boxed in in terms of how we do serialization. Currently, that's used as a
client/server transport mechanism, and not a permanent storage format. Also,
for the metadata APIs, it'd be nice if we could return the value of the
VALUE_EXPRESSION column and see what the expression is. If we use a binary
format, this value will be very opaque. One more factor is in support of
defining a default value at DDL time for a column. I'm hoping we can use this
same column for that as well (but we'll see if this works). In fact, we should
use the same column name: COLUMN_DEF as defined here:
http://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html#getColumns(java.lang.String,%20java.lang.String,%20java.lang.String,%20java.lang.String)
> Support functional indexes
> --------------------------
>
> Key: PHOENIX-514
> URL: https://issues.apache.org/jira/browse/PHOENIX-514
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
> Assignee: Thomas D'Silva
> Labels: enhancement
>
> Instead of only defining the set of columns from the data table that make up
> an index, you should be able to use expressions. For example:
> CREATE INDEX upper_last_name_idx ON person (UPPER(last_name))
> Then in queries that use UPPER(last_name), we can replace them with column
> references to the index table.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
