[ 
https://issues.apache.org/jira/browse/PHOENIX-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268372#comment-17268372
 ] 

ASF GitHub Bot commented on PHOENIX-6323:
-----------------------------------------

gjacoby126 commented on pull request #1095:
URL: https://github.com/apache/phoenix/pull/1095#issuecomment-763349707


   @stoty - it would be very good if we could support the raw filter scans in 
the HBase 2.2 branch. They're required to fix a serious bug where building an 
index on a view can't apply the view's WHERE clause filter condition properly 
to the index, and so you wind up indexing the entire table in each view index, 
wasting lots of storage by creating tons of corrupt index rows (that are never 
read). @abhishek-chouhan discovered and fixed it in PHOENIX-5932. 
   
   Does requiring 2.2.5 on the 2.2 branch create difficulties?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> isRawFilterSupported() returns true for HBase 2.1 comapt module
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-6323
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6323
>             Project: Phoenix
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 5.1.0
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Blocker
>
> org.apache.phoenix.compat.hbase.HbaseCompatCapabilities.isRawFilterSupported()
>  returns true in the HBase 2.2 compatibility module.
> According to the comment this is only available in HBase 2.2.5+, and we 
> support HBase 2.2.1+.
> Either the minimum Supported HBase version has to be bumped to 2.2.5, or the 
> we need to return false.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to