[jira] [Commented] (CALCITE-3117) Distinguish Calcite's public APIs
[ https://issues.apache.org/jira/browse/CALCITE-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858282#comment-16858282 ] Danny Chan commented on CALCITE-3117: - The parser and sql node should be split out of the calcite-core, user usually only want to parse their sql and get a AST. > Distinguish Calcite's public APIs > - > > Key: CALCITE-3117 > URL: https://issues.apache.org/jira/browse/CALCITE-3117 > Project: Calcite > Issue Type: Task >Reporter: Stamatis Zampetakis >Assignee: Stamatis Zampetakis >Priority: Minor > > The goal of this issue is to identify and mark Calcite's public APIs. This > can have bring various benefits to the project: > * provide more flexibility to developers; > * speed-up reviews; > * enhance backward compatibility; > * facilitate the life of end-users who will be exposed to fewer classes and > interfaces. > Let's list here packages, interfaces, and classes that should be part of the > public API. As a first step let's focus exclusively on completing the list > and not argue about others proposals. It will be easier to solve > disagreements afterwards as soon as we have a rather complete list. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-3117) Distinguish Calcite's public APIs
[ https://issues.apache.org/jira/browse/CALCITE-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16857750#comment-16857750 ] Ivan Grgurina commented on CALCITE-3117: RelOptRule and Program should definitely be considered public APIs. > Distinguish Calcite's public APIs > - > > Key: CALCITE-3117 > URL: https://issues.apache.org/jira/browse/CALCITE-3117 > Project: Calcite > Issue Type: Task >Reporter: Stamatis Zampetakis >Assignee: Stamatis Zampetakis >Priority: Minor > > The goal of this issue is to identify and mark Calcite's public APIs. This > can have bring various benefits to the project: > * provide more flexibility to developers; > * speed-up reviews; > * enhance backward compatibility; > * facilitate the life of end-users who will be exposed to fewer classes and > interfaces. > Let's list here packages, interfaces, and classes that should be part of the > public API. As a first step let's focus exclusively on completing the list > and not argue about others proposals. It will be easier to solve > disagreements afterwards as soon as we have a rather complete list. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
