phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3547) Promote CATALOG.VIEW_INDEX_ID to an int
Date Mon, 23 Jul 2018 19:22:00 GMT


ASF GitHub Bot commented on PHOENIX-3547:

GitHub user m2je opened a pull request:

    PHOENIX-3547 Supporting more number of indices per table.
    Currently the number of indices per Phoenix table is bound to maximum of 65535 (java.lang.short)
which may limit some application requiring to have arbitrary unlimited number of indices.

    This change will consider any new table created in Phoenix to support indices ids to be
in  -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 (java.lang.Long) range which is
undoubtably big enough to cover this requirement.
    Any existing Phoenix Phoenix table will still continue to support only maximum of 65535
of indices and will be able to maintain this limits as enforced before. 

You can merge this pull request into a Git repository by running:

    $ git pull support-large-number-of-indecies

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #312
commit 93bf44780867e313cfc3ee31c019c33e28d48e04
Author: Mahdi Salarkia <msalarkia@...>
Date:   2018-07-19T22:23:58Z

    PHOENIX-3547 Supporting more number of indecies per table.


> Promote CATALOG.VIEW_INDEX_ID to an int
> ---------------------------------------
>                 Key: PHOENIX-3547
>                 URL:
>             Project: Phoenix
>          Issue Type: New Feature
>            Reporter: Jeremy Huffman
>            Priority: Minor
> 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