Thanks James. What version of Phoenix are you currently using? --> 2.2.3 incubating
Would it be possible to use uppercase table and column qualifier names as a work around? --> It will be quite some changes at this point in time in our project. The index selection is done in QueryOptimizer, but I doubt the bug would be there. Might be in IndexStatementRewriter which is the code that re-writes a SQL statement to use the index table rather than the data table. --> Thanks. WIll take a look. Regards, Abhilash L L Capillary Technologies M:919886208262 abhil...@capillarytech.com | www.capillarytech.com Email from people at capillarytech.com may not represent official policy of Capillary Technologies unless explicitly stated. Please see our Corporate-Email-Policy <http://support.capillary.co.in/policy-public/Corporate-Email-Policy.pdf> for details. Contents of this email are confidential. Please contact the Sender if you have received this email in error. On Mon, Jun 30, 2014 at 8:28 PM, James Taylor <jamestay...@apache.org> wrote: > Hi, > What version of Phoenix are you currently using? I remember a bug > along these lines that was fixed, but I thought it made it into > 3.0/4.0. Does the problem occur on the latest on the 3.0/4.0 branch? > > The index selection is done in QueryOptimizer, but I doubt the bug > would be there. Might be in IndexStatementRewriter which is the code > that re-writes a SQL statement to use the index table rather than the > data table. > > Would it be possible to use uppercase table and column qualifier names > as a work around? > > Thanks, > James > > On Mon, Jun 30, 2014 at 4:25 PM, Abhilash L L > <abhil...@capillarytech.com> wrote: > > Hello, > > > > Seems like there is an issue in index selection when the columns > involved > > are case sensitive. Here is an example from the one of the slides. > > > > > > ======================================================== > > CREATE TABLE baby_names ( > > name VARCHAR PRIMARY KEY, > > occurrences BIGINT); > > > > CREATE INDEX baby_names_idx ON baby_names(occurrences); > > > > explain SELECT name, occurrences FROM baby_names WHERE occurrences > 100; > > -- CLIENT PARALLEL 1-WAY RANGE SCAN OVER BABY_NAMES_IDX [1E+2] - [*] > > ======================================================== > > > > > > ======================================================== > > CREATE TABLE baby_names ( > > "name" VARCHAR PRIMARY KEY, > > "occurrences" BIGINT); > > > > CREATE INDEX baby_names_idx ON baby_names("occurrences"); > > > > explain SELECT "name", "occurrences" FROM baby_names WHERE "occurrences" > > > > 100; > > -- CLIENT PARALLEL 1-WAY FULL SCAN OVER BABY_NAMES SERVER FILTER BY > > occurrences > 100 > > ======================================================== > > > > We would like to run a patched version of phoenix for now, since we are > > nearing our release date. Would help us a great deal if someone can > point us > > to the class where the index selection is being done. > > > > Regards, > > Abhilash L L > > Capillary Technologies > > M:919886208262 > > abhil...@capillarytech.com | www.capillarytech.com > > > > Email from people at capillarytech.com may not represent official > policy of > > Capillary Technologies unless explicitly stated. Please see our > > Corporate-Email-Policy for details. Contents of this email are > confidential. > > Please contact the Sender if you have received this email in error. > > > > > > Email from people at capillarytech.com may not represent official > policy of > > Capillary Technologies unless explicitly stated. Please see our > > Corporate-Email-Policy for details.Contents of this email are > confidential. > > Please contact the Sender if you have received this email in error. > -- Email from people at capillarytech.com may not represent official policy of Capillary Technologies unless explicitly stated. Please see our Corporate-Email-Policy for details.Contents of this email are confidential. Please contact the Sender if you have received this email in error.
