[jira] [Updated] (HBASE-18966) In-memory compaction/merge should update its TimeRange
[
https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18966:
---
Attachment: HBASE-18966.v1.patch
v1
# address Ted's suggestion.
> In-memory compaction/merge should update its TimeRange
> --
>
> Key: HBASE-18966
> URL: https://issues.apache.org/jira/browse/HBASE-18966
> Project: HBase
> Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18966.v0.patch, HBASE-18966.v1.patch
>
>
> The in-memory compaction/merge do the great job of optimizing the memory
> layout for cells, but they don't update its {{TimeRange}}. It don't cause any
> bugs currently because the {{TimeRange}} is used for store-level ts filter
> only and the default {{TimeRange}} of {{ImmutableSegment}} created by
> in-memory compaction/merge has the maximum ts range.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18966) In-memory compaction/merge should update its TimeRange
[
https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18966:
---
Status: Patch Available (was: Open)
> In-memory compaction/merge should update its TimeRange
> --
>
> Key: HBASE-18966
> URL: https://issues.apache.org/jira/browse/HBASE-18966
> Project: HBase
> Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18966.v0.patch, HBASE-18966.v1.patch
>
>
> The in-memory compaction/merge do the great job of optimizing the memory
> layout for cells, but they don't update its {{TimeRange}}. It don't cause any
> bugs currently because the {{TimeRange}} is used for store-level ts filter
> only and the default {{TimeRange}} of {{ImmutableSegment}} created by
> in-memory compaction/merge has the maximum ts range.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18966) In-memory compaction/merge should update its TimeRange
[
https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18966:
---
Status: Open (was: Patch Available)
> In-memory compaction/merge should update its TimeRange
> --
>
> Key: HBASE-18966
> URL: https://issues.apache.org/jira/browse/HBASE-18966
> Project: HBase
> Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18966.v0.patch
>
>
> The in-memory compaction/merge do the great job of optimizing the memory
> layout for cells, but they don't update its {{TimeRange}}. It don't cause any
> bugs currently because the {{TimeRange}} is used for store-level ts filter
> only and the default {{TimeRange}} of {{ImmutableSegment}} created by
> in-memory compaction/merge has the maximum ts range.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18966) In-memory compaction/merge should update its TimeRange
[
https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18966:
---
Status: Patch Available (was: Open)
> In-memory compaction/merge should update its TimeRange
> --
>
> Key: HBASE-18966
> URL: https://issues.apache.org/jira/browse/HBASE-18966
> Project: HBase
> Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18966.v0.patch
>
>
> The in-memory compaction/merge do the great job of optimizing the memory
> layout for cells, but they don't update its {{TimeRange}}. It don't cause any
> bugs currently because the {{TimeRange}} is used for store-level ts filter
> only and the default {{TimeRange}} of {{ImmutableSegment}} created by
> in-memory compaction/merge has the maximum ts range.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18966) In-memory compaction/merge should update its TimeRange
[
https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18966:
---
Attachment: HBASE-18966.v0.patch
The Non-sync TRT is not heavy-weight than {{TimeRange}}, so the {{TimeRange}}
of {{ImmutableSegment}} can be removed now.
> In-memory compaction/merge should update its TimeRange
> --
>
> Key: HBASE-18966
> URL: https://issues.apache.org/jira/browse/HBASE-18966
> Project: HBase
> Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-18966.v0.patch
>
>
> The in-memory compaction/merge do the great job of optimizing the memory
> layout for cells, but they don't update its {{TimeRange}}. It don't cause any
> bugs currently because the {{TimeRange}} is used for store-level ts filter
> only and the default {{TimeRange}} of {{ImmutableSegment}} created by
> in-memory compaction/merge has the maximum ts range.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18966) In-memory compaction/merge should update its TimeRange
[
https://issues.apache.org/jira/browse/HBASE-18966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai updated HBASE-18966:
---
Description: The in-memory compaction/merge do the great job of optimizing
the memory layout for cells, but they don't update its {{TimeRange}}. It don't
cause any bugs currently because the {{TimeRange}} is used for store-level ts
filter only and the default {{TimeRange}} of {{ImmutableSegment}} created by
in-memory compaction/merge has the maximum ts range.(was: The in-memory
compaction/merge do the great job of optimizing the memory layout for cells,
but they don't update its {{TimeRange}}. It don't cause any bugs currently
because the {{TimeRange}} is used for store-level ts filter only.)
> In-memory compaction/merge should update its TimeRange
> --
>
> Key: HBASE-18966
> URL: https://issues.apache.org/jira/browse/HBASE-18966
> Project: HBase
> Issue Type: Sub-task
>Reporter: Chia-Ping Tsai
>Assignee: Chia-Ping Tsai
> Fix For: 2.0.0-beta-1
>
>
> The in-memory compaction/merge do the great job of optimizing the memory
> layout for cells, but they don't update its {{TimeRange}}. It don't cause any
> bugs currently because the {{TimeRange}} is used for store-level ts filter
> only and the default {{TimeRange}} of {{ImmutableSegment}} created by
> in-memory compaction/merge has the maximum ts range.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
