[jira] [Issue Comment Deleted] (CARBONDATA-4171) Transaction Manager, time travel and segment interface refactoring
[ https://issues.apache.org/jira/browse/CARBONDATA-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajantha Bhat updated CARBONDATA-4171: - Comment: was deleted (was: [^Transaction manager, time travel, segment interface_v2.pdf]) > Transaction Manager, time travel and segment interface refactoring > -- > > Key: CARBONDATA-4171 > URL: https://issues.apache.org/jira/browse/CARBONDATA-4171 > Project: CarbonData > Issue Type: Improvement >Reporter: Ajantha Bhat >Priority: Major > Attachments: Feature impact analysis with segment refactor, time > travel, transaction manager_v1.xlsx, Transaction manager, time travel, > segment interface_v1.pdf > > > *Goals:* > *1) Implement a “Transaction Manager” with optimistic concurrency to provide > within a table transaction / versioning.* (interfaces should also be flexible > enough to support across table transactions) > *2) Support time travel in carbonData.* > *3) Decouple and clean up segment interfaces.* (which should also help in > supporting segment concepts to other open format under carbondata metadata > service) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CARBONDATA-4171) Transaction Manager, time travel and segment interface refactoring
[ https://issues.apache.org/jira/browse/CARBONDATA-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17354426#comment-17354426 ] Ajantha Bhat commented on CARBONDATA-4171: -- [^Transaction manager, time travel, segment interface_v2.pdf] > Transaction Manager, time travel and segment interface refactoring > -- > > Key: CARBONDATA-4171 > URL: https://issues.apache.org/jira/browse/CARBONDATA-4171 > Project: CarbonData > Issue Type: Improvement >Reporter: Ajantha Bhat >Priority: Major > Attachments: Feature impact analysis with segment refactor, time > travel, transaction manager_v1.xlsx, Transaction manager, time travel, > segment interface_v1.pdf > > > *Goals:* > *1) Implement a “Transaction Manager” with optimistic concurrency to provide > within a table transaction / versioning.* (interfaces should also be flexible > enough to support across table transactions) > *2) Support time travel in carbonData.* > *3) Decouple and clean up segment interfaces.* (which should also help in > supporting segment concepts to other open format under carbondata metadata > service) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CARBONDATA-4195) Materialized view loading time increased due to full refresh
Mayuri Patole created CARBONDATA-4195: - Summary: Materialized view loading time increased due to full refresh Key: CARBONDATA-4195 URL: https://issues.apache.org/jira/browse/CARBONDATA-4195 Project: CarbonData Issue Type: Bug Components: core Affects Versions: 2.1.0 Reporter: Mayuri Patole Fix For: 2.1.0 Hi Team, We are using carbon 2.1.0 in our project where parallel data loading is happening. We are working on getting optimal performance for aggregated queries using materialized views. We observed that continues data loading and full refresh of MV is causing increased load time and high memory usage which doesn't have to be this way. Can you suggest a way to perform incremental refresh because we do not need to calculate old data again while loading ? -- This message was sent by Atlassian Jira (v8.3.4#803005)
