zhengruifeng created SPARK-39510: ------------------------------------ Summary: leverage the natural partitioning and ordering of MonotonicallyIncreasingID Key: SPARK-39510 URL: https://issues.apache.org/jira/browse/SPARK-39510 Project: Spark Issue Type: Improvement Components: SQL Affects Versions: 3.4.0 Reporter: zhengruifeng
In Pandas-API-on-Spark: 1, *MonotonicallyIncreasingID* and *AttachDistributedSequence* are widely used as the indexing type for big tables, they naturally have _RangePartitioning_ and _Ascending Ordering._ 2, _Sorting by index_ is a common scenario, such as: 2.1 internally, {color:#00875a}_Window.orderBy(NATURAL_ORDER_COLUMN_NAME)_{color} is widely used in GroupBy, Rolling, Expanding, EWM, etc; 2.2 the __ {color:#00875a}_sort_index_ {color:#172b4d}should be a high frequently used function for end users;{color}{color} {color:#00875a}{color:#172b4d}So we should make *MonotonicallyIncreasingID* and *AttachDistributedSequence* provide the _RangePartitioning_ and _Ascending Ordering, so that the optimizer can leverage them._{color}{color} -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org