FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2
Projects like Phoenix could run would their own versions of libs thereafter (but would no longer be able to depend nor transitively include from hbase). Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if interested/concerned. Thanks, St.Ack
[jira] [Created] (PHOENIX-3780) Undefined Column Error while Using index hint
Manoj Patrick created PHOENIX-3780: -- Summary: Undefined Column Error while Using index hint Key: PHOENIX-3780 URL: https://issues.apache.org/jira/browse/PHOENIX-3780 Project: Phoenix Issue Type: Bug Affects Versions: 4.10.0 Reporter: Manoj Patrick When I force an index with the index hint , I am getting an error. Is this a known error ? Error: ERROR 504 (42703): Undefined column. columnName=:REPORT_INSTANCE_ID (state=42703,code=504) Table Schema: 3 columns: ORGANIZATION_ID,REPORT_INSTANCE_ID,ROWNUM Tenant Specific View Schema: dynamic columns including ACCOUNTNAME index script: create index my_index_filter_1 on pherf.rrs_custom_view1(ACCOUNTNAME) include(ROWNUM); Query: select /*+ INDEX(pherf.rrs_custom_view1 my_index_filter_1) */ ROWNUM from PHERF.RRS_CUSTOM_VIEW1 where ACCOUNTNAME = 'Account_7' ORDER BY CUSTOMFIELD2; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (PHOENIX-3780) Undefined Column Error while Using index hint
[ https://issues.apache.org/jira/browse/PHOENIX-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964922#comment-15964922 ] Manoj Patrick commented on PHOENIX-3780: I will upload the needed data sets to reproduce the issue. > Undefined Column Error while Using index hint > -- > > Key: PHOENIX-3780 > URL: https://issues.apache.org/jira/browse/PHOENIX-3780 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.10.0 >Reporter: Manoj Patrick > > When I force an index with the index hint , I am getting an error. Is this a > known error ? > Error: ERROR 504 (42703): Undefined column. columnName=:REPORT_INSTANCE_ID > (state=42703,code=504) > > Table Schema: > 3 columns: ORGANIZATION_ID,REPORT_INSTANCE_ID,ROWNUM > > Tenant Specific View Schema: dynamic columns including ACCOUNTNAME > > index script: create index my_index_filter_1 on > pherf.rrs_custom_view1(ACCOUNTNAME) include(ROWNUM); > > Query: select /*+ INDEX(pherf.rrs_custom_view1 my_index_filter_1) */ ROWNUM > from PHERF.RRS_CUSTOM_VIEW1 where ACCOUNTNAME = 'Account_7' ORDER BY > CUSTOMFIELD2; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (PHOENIX-3780) Undefined Column Error while Using index hint
[ https://issues.apache.org/jira/browse/PHOENIX-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Patrick updated PHOENIX-3780: --- Attachment: Analytics_reports_scenario.xml create_pherf_REPORT_INSTANCE_DATA_DETAIL.sql This is how you need to setup the data: Step1: Deploy the phoenix Schema and Scenario File to create the Table and the View. Step2: To Load the generated data , run the following Pherf script, The scenario files also has Query Sets defined , Please do not run those. Just use the scenario file to load data into the view. Step 3: create index my_index_filter_1 on pherf.rrs_custom_view1(ACCOUNTNAME) include(ROWNUM); Step4: Run a query on the view having the index. select /*+ INDEX(pherf.rrs_custom_view1 my_index_filter_1) */ ROWNUM from PHERF.RRS_CUSTOM_VIEW1 where ACCOUNTNAME = 'Account_7' ORDER BY CUSTOMFIELD2; > Undefined Column Error while Using index hint > -- > > Key: PHOENIX-3780 > URL: https://issues.apache.org/jira/browse/PHOENIX-3780 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.10.0 >Reporter: Manoj Patrick > Attachments: Analytics_reports_scenario.xml, > create_pherf_REPORT_INSTANCE_DATA_DETAIL.sql > > > When I force an index with the index hint , I am getting an error. Is this a > known error ? > Error: ERROR 504 (42703): Undefined column. columnName=:REPORT_INSTANCE_ID > (state=42703,code=504) > > Table Schema: > 3 columns: ORGANIZATION_ID,REPORT_INSTANCE_ID,ROWNUM > > Tenant Specific View Schema: dynamic columns including ACCOUNTNAME > > index script: create index my_index_filter_1 on > pherf.rrs_custom_view1(ACCOUNTNAME) include(ROWNUM); > > Query: select /*+ INDEX(pherf.rrs_custom_view1 my_index_filter_1) */ ROWNUM > from PHERF.RRS_CUSTOM_VIEW1 where ACCOUNTNAME = 'Account_7' ORDER BY > CUSTOMFIELD2; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (PHOENIX-3780) Undefined Column Error while Using index hint
[ https://issues.apache.org/jira/browse/PHOENIX-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-3780: - Assignee: Loknath Priyatham Teja Singamsetty > Undefined Column Error while Using index hint > -- > > Key: PHOENIX-3780 > URL: https://issues.apache.org/jira/browse/PHOENIX-3780 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.10.0 >Reporter: Manoj Patrick >Assignee: Loknath Priyatham Teja Singamsetty > Attachments: Analytics_reports_scenario.xml, > create_pherf_REPORT_INSTANCE_DATA_DETAIL.sql > > > When I force an index with the index hint , I am getting an error. Is this a > known error ? > Error: ERROR 504 (42703): Undefined column. columnName=:REPORT_INSTANCE_ID > (state=42703,code=504) > > Table Schema: > 3 columns: ORGANIZATION_ID,REPORT_INSTANCE_ID,ROWNUM > > Tenant Specific View Schema: dynamic columns including ACCOUNTNAME > > index script: create index my_index_filter_1 on > pherf.rrs_custom_view1(ACCOUNTNAME) include(ROWNUM); > > Query: select /*+ INDEX(pherf.rrs_custom_view1 my_index_filter_1) */ ROWNUM > from PHERF.RRS_CUSTOM_VIEW1 where ACCOUNTNAME = 'Account_7' ORDER BY > CUSTOMFIELD2; -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2
Thanks for the heads-up, Stack. Josh is our resident shading expert - hopefully he'll chime in based on his experience/expertise. James On Tue, Apr 11, 2017 at 1:03 PM, Stack wrote: > Projects like Phoenix could run would their own versions of libs thereafter > (but would no longer be able to depend nor transitively include from > hbase). > > Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if > interested/concerned. > > Thanks, > St.Ack >
[jira] [Updated] (PHOENIX-3781) Backward compatibility issue with old client and 4.10 server
[ https://issues.apache.org/jira/browse/PHOENIX-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samarth Jain updated PHOENIX-3781: -- Attachment: PHOENIX-3781.patch [~jamestaylor], please review. > Backward compatibility issue with old client and 4.10 server > > > Key: PHOENIX-3781 > URL: https://issues.apache.org/jira/browse/PHOENIX-3781 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.10.0 >Reporter: Samarth Jain >Assignee: Samarth Jain > Fix For: 4.11.0, 4.10.1 > > Attachments: PHOENIX-3781.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (PHOENIX-3781) Backward compatibility issue with old client and 4.10 server
Samarth Jain created PHOENIX-3781: - Summary: Backward compatibility issue with old client and 4.10 server Key: PHOENIX-3781 URL: https://issues.apache.org/jira/browse/PHOENIX-3781 Project: Phoenix Issue Type: Bug Affects Versions: 4.10.0 Reporter: Samarth Jain Assignee: Samarth Jain Fix For: 4.11.0, 4.10.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (PHOENIX-3781) Backward compatibility issue with old client and 4.10 server
[ https://issues.apache.org/jira/browse/PHOENIX-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965216#comment-15965216 ] James Taylor commented on PHOENIX-3781: --- +1. Is the plan to manually verify the fix? > Backward compatibility issue with old client and 4.10 server > > > Key: PHOENIX-3781 > URL: https://issues.apache.org/jira/browse/PHOENIX-3781 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.10.0 >Reporter: Samarth Jain >Assignee: Samarth Jain > Fix For: 4.11.0, 4.10.1 > > Attachments: PHOENIX-3781.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (PHOENIX-3781) Backward compatibility issue with old client and 4.10 server
[ https://issues.apache.org/jira/browse/PHOENIX-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965246#comment-15965246 ] Samarth Jain commented on PHOENIX-3781: --- Yes. > Backward compatibility issue with old client and 4.10 server > > > Key: PHOENIX-3781 > URL: https://issues.apache.org/jira/browse/PHOENIX-3781 > Project: Phoenix > Issue Type: Bug >Affects Versions: 4.10.0 >Reporter: Samarth Jain >Assignee: Samarth Jain > Fix For: 4.11.0, 4.10.1 > > Attachments: PHOENIX-3781.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: FYI: HBase looking to shade/hide/remove core libs like netty and guava in hbase2
Sergey too. ;) Will catch up over on dev@hbase. Thanks for making sure we were aware of this one downstream, Stack. On Apr 11, 2017 19:53, "James Taylor" wrote: > Thanks for the heads-up, Stack. Josh is our resident shading expert - > hopefully he'll chime in based on his experience/expertise. > > James > > On Tue, Apr 11, 2017 at 1:03 PM, Stack wrote: > >> Projects like Phoenix could run would their own versions of libs >> thereafter >> (but would no longer be able to depend nor transitively include from >> hbase). >> >> Discussion is ongoing (See "[DISCUSS] More Shading"). Pitch in please if >> interested/concerned. >> >> Thanks, >> St.Ack >> > >
