[jira] [Resolved] (HBASE-23251) Add Column Family and Table Names to HFileContext and use in HFileWriterImpl logging
[ https://issues.apache.org/jira/browse/HBASE-23251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zheng Hu resolved HBASE-23251. -- Hadoop Flags: Reviewed Resolution: Fixed > Add Column Family and Table Names to HFileContext and use in HFileWriterImpl > logging > > > Key: HBASE-23251 > URL: https://issues.apache.org/jira/browse/HBASE-23251 > Project: HBase > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Geoffrey Jacoby >Assignee: Geoffrey Jacoby >Priority: Major > Fix For: 3.0.0, 2.3.0 > > Attachments: HBASE-23251.v01.patch > > > When something goes wrong in the Store / HFile write path, it would be very > useful to know which column family and table the error is coming from. > Currently the HFileWriterImpl gets an HFileContext object with some useful > state information, but the column family and table aren't among them. > For example, this would be very helpful diagnosing HBASE-23143 and similar > issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23074) scan#setVersion is invalid.
[
https://issues.apache.org/jira/browse/HBASE-23074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guangxu Cheng resolved HBASE-23074.
---
Resolution: Duplicate
> scan#setVersion is invalid.
> ---
>
> Key: HBASE-23074
> URL: https://issues.apache.org/jira/browse/HBASE-23074
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1, master
>Reporter: Bo Cui
>Priority: Critical
> Attachments: image-2019-09-25-16-45-08-870.png,
> image-2019-09-25-16-45-37-780.png
>
>
> I found a problem, it could be a mistake..
> reproduce steps in hbase shell:
> 1. create 't11', \{NAME => 'f1', VERSIONS => 1}
> 2.put 't11','r1','f1:q1','f1'
> 3.flush 't11'
> 4.put 't11','r1','f1:q1','f2'
> 5.flush 't11'
> 6.scan 't11', \{RAW => true, VERSIONS => 10, FILTER => "(QualifierFilter (>=,
> 'binary:f1'))"}
>
> the result:
> 1. 1.3.1 version
> hbase(main):011:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER =>
> "(QualifierFilter (>=, 'binary:q1'))"}
> ROW COLUMN+CELL
> r1 column=f1:q1, timestamp=1569400085570, value=f2
> r1 column=f1:q1, timestamp=1569400068958, value=f1
> 2. in 2.1.1 version
> hbase(main):023:0> scan 't11', \{RAW => true, VERSIONS => 10, FILTER =>
> "(QualifierFilter (>=, 'binary:q1'))"}
> ROW COLUMN+CELL
> r1 column=f1:q1, timestamp=1569400122280, value=f2
> 1 row(s)
> Took 0.0800 seconds
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (HBASE-23279) Switch default block encoding to ROW_INDEX_V1
Lars Hofhansl created HBASE-23279: - Summary: Switch default block encoding to ROW_INDEX_V1 Key: HBASE-23279 URL: https://issues.apache.org/jira/browse/HBASE-23279 Project: HBase Issue Type: Improvement Reporter: Lars Hofhansl Currently we set both block encoding and compression to NONE. ROW_INDEX_V1 has many advantages and (almost) no disadvantages (the hfiles are slightly larger about 3% or so). I think that would a better default than NONE. -- This message was sent by Atlassian Jira (v8.3.4#803005)
