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

Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/11/17 12:31:33 UTC

[jira] [Updated] (TAJO-1177) Reduce the use of Sun proprietary API

     [ https://issues.apache.org/jira/browse/TAJO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-1177:
-------------------------------
    Fix Version/s: 0.9.1

> Reduce the use of Sun proprietary API
> -------------------------------------
>
>                 Key: TAJO-1177
>                 URL: https://issues.apache.org/jira/browse/TAJO-1177
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Jihun Kang
>            Assignee: Jihun Kang
>            Priority: Minor
>             Fix For: 0.9.1
>
>
> Sometimes JVM developers tend to change their internal method signatures or implementations for performance issues or design issues when upgrading version of JVM. So if java class library provides public api for its implementation, I think that using public api might be a good choice to avoid compatibility issues.



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