[
https://issues.apache.org/jira/browse/CARBONDATA-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenzhengyu updated CARBONDATA-4260:
------------------------------------
Affects Version/s: 2.4.0
> Support Trino To Replace PrestoSQL
> ----------------------------------
>
> Key: CARBONDATA-4260
> URL: https://issues.apache.org/jira/browse/CARBONDATA-4260
> Project: CarbonData
> Issue Type: New Feature
> Affects Versions: 2.4.0
> Environment: Must be use JDK 11.0.11 + to build mvn
> Reporter: chenzhengyu
> Assignee: chenzhengyu
> Priority: Critical
> Labels: Presto, Trino
>
> h3. Why is this PR needed?
> PrestoSQL has now changed its name to Trino. Because Facebook established the
> Presto Foundation at The Linux Foundation®,Led to prestosql Must be change
> the name
> More information can see
> [here|https://trino.io/blog/2020/12/27/announcing-trino.html]
> I'm here to suggest that we replace the old PrestoSQL implementation with a
> new Trino, which will keep our CarbonData community in sync with the open
> source community's technical path
> CarbonData currently supports querying Hive/Spark data using PrestoSQL (316),
> but many new features and performance improvements are not available to users
> due to the new version of CarbonData
> (!) We will first provide a beta version of CarbonData on the branch. You are
> welcome to use the test, wait for the completion of the test and use cases,
> we will officially merge into the trunk branch when the functionality is
> stable
> h3. What changes were proposed in this PR?
> * Java 11 removed ConstructorAccessor class,use unsafe class for reflection
> * Rename the file Trino beginning with Presto
> * Unify file hump case style and Divide component package names
> * CarbonDataSplitManager add properties serialization.lib about
> StorageFormatSerDe
> * TrinoFilterUtil Logical Changes to determine Rang
> * Maven Pom Support Trino 358
> h3. Does this PR introduce any user interface change?
> * No
> h3. Is any new testcase added?
> * No
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)