[jira] [Updated] (HBASE-10487) Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing values
[ https://issues.apache.org/jira/browse/HBASE-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-10487: --- Fix Version/s: 0.98.1 Hadoop Flags: Reviewed > Avoid allocating new KeyValue and according bytes-copying for appended kvs > which don't have existing values > --- > > Key: HBASE-10487 > URL: https://issues.apache.org/jira/browse/HBASE-10487 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Feng Honghua >Assignee: Feng Honghua > Fix For: 0.98.1, 0.99.0 > > Attachments: HBASE-10487-0.98_v1.patch, HBASE-10487-trunk_v1.patch > > > in HRegion.append, new KeyValues will be allocated and do according > bytes-copying no matter whether there are existing kv for the appended cells, > we can improve here by avoiding the allocating of new KeyValue and according > bytes-copying for kv which don't have existing(old) values by reusing the > passed-in kv and only updating its timestamp to 'now'(its original timestamp > is latest, so can be updated) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HBASE-10487) Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing values
[ https://issues.apache.org/jira/browse/HBASE-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-10487: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Avoid allocating new KeyValue and according bytes-copying for appended kvs > which don't have existing values > --- > > Key: HBASE-10487 > URL: https://issues.apache.org/jira/browse/HBASE-10487 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Feng Honghua >Assignee: Feng Honghua > Fix For: 0.98.1, 0.99.0 > > Attachments: HBASE-10487-0.98_v1.patch, HBASE-10487-trunk_v1.patch > > > in HRegion.append, new KeyValues will be allocated and do according > bytes-copying no matter whether there are existing kv for the appended cells, > we can improve here by avoiding the allocating of new KeyValue and according > bytes-copying for kv which don't have existing(old) values by reusing the > passed-in kv and only updating its timestamp to 'now'(its original timestamp > is latest, so can be updated) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HBASE-10487) Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing values
[ https://issues.apache.org/jira/browse/HBASE-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Feng Honghua updated HBASE-10487: - Attachment: HBASE-10487-0.98_v1.patch Patch for 0.98 attached, thanks [~yuzhih...@gmail.com] > Avoid allocating new KeyValue and according bytes-copying for appended kvs > which don't have existing values > --- > > Key: HBASE-10487 > URL: https://issues.apache.org/jira/browse/HBASE-10487 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Feng Honghua >Assignee: Feng Honghua > Fix For: 0.99.0 > > Attachments: HBASE-10487-0.98_v1.patch, HBASE-10487-trunk_v1.patch > > > in HRegion.append, new KeyValues will be allocated and do according > bytes-copying no matter whether there are existing kv for the appended cells, > we can improve here by avoiding the allocating of new KeyValue and according > bytes-copying for kv which don't have existing(old) values by reusing the > passed-in kv and only updating its timestamp to 'now'(its original timestamp > is latest, so can be updated) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HBASE-10487) Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing values
[ https://issues.apache.org/jira/browse/HBASE-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-10487: --- Fix Version/s: 0.99.0 > Avoid allocating new KeyValue and according bytes-copying for appended kvs > which don't have existing values > --- > > Key: HBASE-10487 > URL: https://issues.apache.org/jira/browse/HBASE-10487 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Feng Honghua >Assignee: Feng Honghua > Fix For: 0.99.0 > > Attachments: HBASE-10487-trunk_v1.patch > > > in HRegion.append, new KeyValues will be allocated and do according > bytes-copying no matter whether there are existing kv for the appended cells, > we can improve here by avoiding the allocating of new KeyValue and according > bytes-copying for kv which don't have existing(old) values by reusing the > passed-in kv and only updating its timestamp to 'now'(its original timestamp > is latest, so can be updated) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HBASE-10487) Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing values
[ https://issues.apache.org/jira/browse/HBASE-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated HBASE-10487: --- Summary: Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing values (was: Avoid allocating new KeyValue and according bytes-copying for appended kvs which don't have existing(old) values) > Avoid allocating new KeyValue and according bytes-copying for appended kvs > which don't have existing values > --- > > Key: HBASE-10487 > URL: https://issues.apache.org/jira/browse/HBASE-10487 > Project: HBase > Issue Type: Improvement > Components: regionserver >Reporter: Feng Honghua >Assignee: Feng Honghua > Attachments: HBASE-10487-trunk_v1.patch > > > in HRegion.append, new KeyValues will be allocated and do according > bytes-copying no matter whether there are existing kv for the appended cells, > we can improve here by avoiding the allocating of new KeyValue and according > bytes-copying for kv which don't have existing(old) values by reusing the > passed-in kv and only updating its timestamp to 'now'(its original timestamp > is latest, so can be updated) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
