phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2163) Measure performance of Phoenix/Calcite querying
Date Tue, 26 Jan 2016 03:18:40 GMT


Maryann Xue commented on PHOENIX-2163:

I filed PHOENIX-2530 a while ago to track missing support for a couple of scalar functions
in Calcite. PHOENIX-2530 is now listed as a sub-task under this issue, alternatively I could
close this entry and make PHOENIX-2530 an independent issue but link one to another. Which
way do you prefer, [~jamestaylor]?

> Measure performance of Phoenix/Calcite querying
> -----------------------------------------------
>                 Key: PHOENIX-2163
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Maryann Xue
>              Labels: calcite
>         Attachments: PHOENIX-2163.patch, PhoenixRegressor.log, calcite-test-mac.tar.gz,
hbase-logs.7167262.tar.gz, publish.7167262.tar.gz
> The work to integrate Phoenix with Calcite has come along far enough that queries both
against the data table and through a secondary index is functional. As a checkpoint, we should
compare performance of as many queries as possible in our regression suite for the calcite
branch against the latest Phoenix release (4.5.0). The runtime of these two systems should
be the same, so this will give us an idea of the overhead of query parsing and compilation
for Calcite. This is super important, as it'll identify outstanding work that'll be necessary
to do prior to any releases on top of this new stack.
> Source code of regression suite is at
> Connection string location:
> Instructions on how to compile and run:

This message was sent by Atlassian JIRA

View raw message