[
https://issues.apache.org/jira/browse/TAJO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212327#comment-14212327
]
ASF GitHub Bot commented on TAJO-1177:
--------------------------------------
GitHub user ykrips opened a pull request:
https://github.com/apache/tajo/pull/243
TAJO-1177: Reduce the use of Sun proprietary API
It has been passed test cases using JDK 1.6.0_45.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ykrips/tajo TAJO-1177
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/243.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #243
----
commit e7a5f8a39649cadf7acc6a29e388e130dcd2d2bc
Author: Jihun Kang <[email protected]>
Date: 2014-11-14T14:50:35Z
TAJO-1177: Reduce the use of Sun proprietary API
----
> 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
>
> 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)
