Hey guys..we figured it out. There is definitely a comparison contract violation with the JTS libraries using JDK 1.7 due to themove to default TimSort. See my previous email which I think is awaiting moderation due to its length. However, if you getinto a situation running this out of a UDF in Hadoop Hive using JDK 1.7, the mistake we made was toset mapred.child.java.opts='-Djava.util.Arrays.useLegacyMergeSort=true -Xmx8g ..and so on';If you put single quotes around the options, the useLegacyMergeSort=true does not take effect. Simply remove the singlequotes and JTS will no longer use TimSort in JDK 1.7 and should have the same memory footprint and performance as it did inJDK 1.6. Also the comparison contract violation will not occur as MergeSort is not as strict.