Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18571
I checked other dbms (dbms-like) systems handled binary as unassigned;
```
postgres=# SELECT E'\\x00'::BYTEA < E'\\xff'::BYTEA;
?column?
----------
t
(1 row)
hive> SELECT unhex('00') < unhex('ff');
OK
true
mysql> SELECT x'00' < x'ff';
+---------------+
| x'00' < x'ff' |
+---------------+
| 1 |
+---------------+
```
In some parts of the Spark implementation, they also handle binary as
unassigned
(https://github.com/apache/spark/blob/master/core/src/main/java/org/apache/spark/util/collection/unsafe/sort/PrefixComparators.java#L36).
I feel, based on the principle of least astonishment, we'd be better to handle
binary as unassigned in user-facing pieces.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
