[
https://issues.apache.org/jira/browse/PARQUET-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15854711#comment-15854711
]
Ryan Blue edited comment on PARQUET-686 at 2/6/17 10:06 PM:
------------------------------------------------------------
[~julianhyde], I'm not sure that we should make this SQL-specific. Right now,
the PR allows a String identifier for custom sort orders, so this example could
be expressed as "sql:SQL_Latin1_General_CP1_CI_AS". Does that work?
Also, I'd like to find a spec for these, even if it is just a page documenting
what postgres or some other implementation does.
**Edit**: Fixed the example, since {{SQL_Latin1_General_CP1_CI_AS}} is one
collating sequence
was (Author: rdblue):
[~julianhyde], I'm not sure that we should make this SQL-specific. Right now,
the PR allows a String identifier for custom sort orders, so this example could
be expressed as "sql:SQL_Latin1_General_CP1_CI_AS". Does that work?
Also, I'd like to find a spec for these, even if it is just a page documenting
what postgres or some other implementation does.
> Allow for Unsigned Statistics in Binary Type
> --------------------------------------------
>
> Key: PARQUET-686
> URL: https://issues.apache.org/jira/browse/PARQUET-686
> Project: Parquet
> Issue Type: Bug
> Reporter: Andrew Duffy
>
> BinaryStatistics currently only have a min/max, which are compared as signed
> {{byte[]}}. However, for real UTF8-friendly lexicographic comparison, e.g.
> for string columns, we would want to calculate the BinaryStatistics based off
> of a comparator that treats the bytes as unsigned.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
