[
https://issues.apache.org/jira/browse/TAJO-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214566#comment-14214566
]
Hudson commented on TAJO-1177:
------------------------------
FAILURE: Integrated in Tajo-master-CODEGEN-build #94 (See
[https://builds.apache.org/job/Tajo-master-CODEGEN-build/94/])
TAJO-1177: Reduce the use of Sun proprietary API. (Jihun Kang via hyunsik)
(hyunsik: rev a0625a620bba9781c51f2ee0f47ec0aad1c36767)
* tajo-storage/src/main/java/org/apache/tajo/tuple/offheap/UnSafeTuple.java
* tajo-storage/src/main/java/org/apache/tajo/tuple/offheap/HeapTuple.java
* tajo-common/src/main/java/org/apache/tajo/util/UnsafeUtil.java
* CHANGES
* tajo-core/src/test/java/org/apache/tajo/client/TestTajoClient.java
* tajo-common/src/main/java/org/apache/tajo/datum/TextDatum.java
* tajo-common/src/test/java/org/apache/tajo/util/TestStringUtil.java
* tajo-common/src/main/java/org/apache/tajo/util/StringUtils.java
* tajo-common/src/test/java/org/apache/tajo/datum/TestTextDatum.java
* tajo-common/src/main/java/org/apache/tajo/util/KeyValueSet.java
> 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)
