[
https://issues.apache.org/jira/browse/HBASE-23583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998226#comment-16998226
]
Peter Somogyi commented on HBASE-23583:
---------------------------------------
FilterListWithOR and FilterListWithAND are internal classes. IIRC you should
only use FilterList. Could you check if it works that way?
{{new FilterList(Operator.MUST_PASS_ONE, filters)}}
> FilterList implementations lack `parseFrom`
> -------------------------------------------
>
> Key: HBASE-23583
> URL: https://issues.apache.org/jira/browse/HBASE-23583
> Project: HBase
> Issue Type: Bug
> Components: Client, Filters
> Affects Versions: 2.2.3
> Reporter: Nick Dimiduk
> Priority: Major
>
> Trying to make use of {{FilterListWithAND}}, I get a nasty stack trace that
> ends in
> {noformat}
> Caused by: org.apache.hadoop.hbase.exceptions.DeserializationException:
> parseFrom called on base Filter, but should be called on derived type
> at org.apache.hadoop.hbase.filter.Filter.parseFrom(Filter.java:304)
> ... 13 more
> at
> org.apache.hadoop.hbase.master.webapp.MetaBrowser$ResultConsumer.onError(MetaBrowser.java:312)
> at
> org.apache.hadoop.hbase.client.AsyncTableImpl.scan0(AsyncTableImpl.java:191)
> at
> org.apache.hadoop.hbase.client.AsyncTableImpl.lambda$scan$0(AsyncTableImpl.java:197)
> {noformat}
> Same thing happens with {{FilterListWithOR}}. It appears as if their
> implementations were not finished during the port over to protobuf. Sadly, I
> find no tests for these classes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
