phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3547) Promote CATALOG.VIEW_INDEX_ID to an int
Date Sat, 19 Jan 2019 00:06:00 GMT


Thomas D'Silva commented on PHOENIX-3547:

[~m2je] Did you test this scenario while you were testing b/w compatibility testing? If the
server has a new version and creates an index that uses int as the id, will an old client
be able to use the index? Instead of using int by default while creating an index, can we
just default to short ?

> Promote CATALOG.VIEW_INDEX_ID to an int
> ---------------------------------------
>                 Key: PHOENIX-3547
>                 URL:
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Jeremy Huffman
>            Assignee: Mehdi Salarkia
>            Priority: Minor
>             Fix For: 4.15.0, 5.1.0
>         Attachments: 4.x-HBase-0.98.patch, 4.x-HBase-1.1.patch, 4.x-HBase-1.2.patch,
4.x-HBase-1.3.patch, 4.x-HBase-1.4.patch, 4.x-cdh5.11.patch, 4.x-cdh5.12.patch, 4.x-cdh5.13.patch,
4.x-cdh5.14.patch, master-PHOENIX-3547.patch
> Increase the size of CATALOG.VIEW_INDEX_ID from smallint to int to support a large number
of indexed views on a single table.
> Per James: "The code would just need to be tolerant when reading the data if the length
is two byte short versus four byte int. At write time, we'd just always write an int."
> See:

This message was sent by Atlassian JIRA

View raw message