You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/03/23 23:33:55 UTC

[jira] [Commented] (CALCITE-639) Open up permissions on avatica server components

    [ https://issues.apache.org/jira/browse/CALCITE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376794#comment-14376794 ] 

Julian Hyde commented on CALCITE-639:
-------------------------------------

These changes increase the surface area of the API. People will presume that these are public APIs and complain if they change.

Can we introduce a maturity model?

> Open up permissions on avatica server components
> ------------------------------------------------
>
>                 Key: CALCITE-639
>                 URL: https://issues.apache.org/jira/browse/CALCITE-639
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>         Attachments: CALCITE-639.00.patch
>
>
> For users who want more fine-grained control over their Avatica server instance, we should open up the class-level protections on relevant classes. That way folks can instantiate/subclass as they require.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)