rdblue commented on a change in pull request #2055:
URL: https://github.com/apache/iceberg/pull/2055#discussion_r559029224



##########
File path: site/docs/spec.md
##########
@@ -831,6 +852,29 @@ Each partition field in the fields list is stored as an 
object. See the table fo
 In some cases partition specs are stored using only the field list instead of 
the object format that includes the spec ID, like the deprecated 
`partition-spec` field in table metadata. The object format should be used 
unless otherwise noted in this spec.
 
 
+### Sort Orders
+
+Sort orders are serialized as a list of JSON object, each of which contains 
the following fields:
+
+|Field|JSON representation|Example|
+|--- |--- |--- |
+|**`order-id`**|`JSON int`|`1`|
+|**`fields`**|`JSON list: [`<br />&nbsp;&nbsp;`<sort field JSON>,`<br 
/>&nbsp;&nbsp;`...`<br />`]`|`[ {`<br />&nbsp;&nbsp;`  "transform": 
"identity",`<br />&nbsp;&nbsp;`  "source-id": 2,`<br />&nbsp;&nbsp;`  
"direction": "asc",`<br />&nbsp;&nbsp;`  "null-order": "nulls-first"`<br 
/>&nbsp;&nbsp;`}, {`<br />&nbsp;&nbsp;`  "transform": "bucket[4]",`<br 
/>&nbsp;&nbsp;`  "source-id": 3,`<br />&nbsp;&nbsp;`  "direction": "desc",`<br 
/>&nbsp;&nbsp;`  "null-order": "nulls-last"`<br />`} ]`|
+
+Each sort field in the fields list is stored as an object with the following 
properties:
+
+|Field|JSON representation|Example|
+|--- |--- |--- |
+|**`Sort Field`**|`JSON object: {`<br />&nbsp;&nbsp;`"transform": <transform 
JSON>,`<br />&nbsp;&nbsp;`"source-id": <source id int>,`<br 
/>&nbsp;&nbsp;`"direction": <direction string>,`<br 
/>&nbsp;&nbsp;`"null-order": <null-order string>`<br />`}`|`{`<br 
/>&nbsp;&nbsp;`  "transform": "bucket[4]",`<br />&nbsp;&nbsp;`  "source-id": 
3,`<br />&nbsp;&nbsp;`  "direction": "desc",`<br />&nbsp;&nbsp;`  "null-order": 
"nulls-last"`<br />`}`|
+
+The following table describes the possible values for the some of the field 
within sort field: 
+
+|Field|JSON representation|Possible values|
+|--- |--- |--- |
+|**`direction`**|`JSON string`|`"asc", "desc"`|
+|**`null-order`**|`JSON string`|`"nulls-first", "nulls-last"`|

Review comment:
       The `Float.compare` implementation in Java will sort `NaN` larger than 
any other value and `-NaN` smaller than any other value. I think we should go 
with that.
   
   ```java
       public static int compare(float f1, float f2) {
           if (f1 < f2)
               return -1;           // Neither val is NaN, thisVal is smaller
           if (f1 > f2)
               return 1;            // Neither val is NaN, thisVal is larger
   
           // Cannot use floatToRawIntBits because of possibility of NaNs.
           int thisBits    = Float.floatToIntBits(f1);
           int anotherBits = Float.floatToIntBits(f2);
   
           return (thisBits == anotherBits ?  0 : // Values are equal
                   (thisBits < anotherBits ? -1 : // (-0.0, 0.0) or (!NaN, NaN)
                    1));                          // (0.0, -0.0) or (NaN, !NaN)
       }
   ```
   
   I think that produces: -NaN < -Infinity < -value < -0 < 0 < value < Infinity 
< NaN




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to