You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/03 10:46:02 UTC
[jira] [Updated] (FLINK-18939) Sort-partition result is incorrect
when use Bigdecimal as Key
[ https://issues.apache.org/jira/browse/FLINK-18939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-18939:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> Sort-partition result is incorrect when use Bigdecimal as Key
> -------------------------------------------------------------
>
> Key: FLINK-18939
> URL: https://issues.apache.org/jira/browse/FLINK-18939
> Project: Flink
> Issue Type: Bug
> Components: API / DataSet
> Affects Versions: 1.9.1
> Reporter: Shengnan YU
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> result of Dataset sort-partition method gives incorrect result when use BigDecimal as key.
> Here is the test code. The print result does not give the right order.
> {code:java}
> ExecutionEnvironment env = ExecutionEnvironment.getExecutionEnvironment();
> DataSet<String> ss = env.fromElements("1234567.89", "3456789.12", "2345678.91");
> DataSet<String> result = ss.sortPartition(new KeySelector<String,BigDecimal>() {
> @Override
> public BigDecimal getKey(String value) throws Exception {
> return new BigDecimal(value);
> }
> }, Order.ASCENDING).setParallelism(1);
> result.print();
> {code}
> It seems that class BigDecComprator some problem and the normalized key cannot be compared correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)