You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org> on 2009/07/29 00:29:14 UTC
[jira] Created: (AVRO-85) A few minor errors in and suggestions for
the spec document
A few minor errors in and suggestions for the spec document
-----------------------------------------------------------
Key: AVRO-85
URL: https://issues.apache.org/jira/browse/AVRO-85
Project: Avro
Issue Type: Bug
Reporter: Thiruvalluvan M. G.
There are a few minor errors in the specifications document:
- The 32-bit and 64-bit floating point numbers should mention the exact IEEE standard (i.e IEEE 754 instead of plain IEEE).
- It'll be clearer if we state that the long value preceding string or bytes is the number of bytes being encoded.
- In the binary serialization example for unicode string "foo" the length 3 will get encoded as 0x06 not 0x0c.
- We should be more specific about how one serializes float and double, Unfortunately, the IEEE 754 does not specify byte ordering. At least we can point to {html} <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html#doubleToRawLongBits%28double%29" /> {html} for details.
- In the resolution section, we should mention how default values for record fields get used
- There is a sudden mention of "method parameters" in the resolution of records; the reader won't have a clue what it refers to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-85) A few minor errors in and suggestions for
the spec document
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated AVRO-85:
-----------------------------
Fix Version/s: 1.0.1
> A few minor errors in and suggestions for the spec document
> -----------------------------------------------------------
>
> Key: AVRO-85
> URL: https://issues.apache.org/jira/browse/AVRO-85
> Project: Avro
> Issue Type: Bug
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Fix For: 1.0.1
>
> Attachments: AVRO-85.patch
>
>
> There are a few minor errors in the specifications document:
> - The 32-bit and 64-bit floating point numbers should mention the exact IEEE standard (i.e IEEE 754 instead of plain IEEE).
> - It'll be clearer if we state that the long value preceding string or bytes is the number of bytes being encoded.
> - In the binary serialization example for unicode string "foo" the length 3 will get encoded as 0x06 not 0x0c.
> - We should be more specific about how one serializes float and double, Unfortunately, the IEEE 754 does not specify byte ordering. At least we can point to {html} <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html#doubleToRawLongBits%28double%29" /> {html} for details.
> - In the resolution section, we should mention how default values for record fields get used
> - There is a sudden mention of "method parameters" in the resolution of records; the reader won't have a clue what it refers to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-85) A few minor errors in and suggestions for
the spec document
Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiruvalluvan M. G. updated AVRO-85:
------------------------------------
Attachment: AVRO-85.patch
Here is a patch that fixes the spec document.
> A few minor errors in and suggestions for the spec document
> -----------------------------------------------------------
>
> Key: AVRO-85
> URL: https://issues.apache.org/jira/browse/AVRO-85
> Project: Avro
> Issue Type: Bug
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Attachments: AVRO-85.patch
>
>
> There are a few minor errors in the specifications document:
> - The 32-bit and 64-bit floating point numbers should mention the exact IEEE standard (i.e IEEE 754 instead of plain IEEE).
> - It'll be clearer if we state that the long value preceding string or bytes is the number of bytes being encoded.
> - In the binary serialization example for unicode string "foo" the length 3 will get encoded as 0x06 not 0x0c.
> - We should be more specific about how one serializes float and double, Unfortunately, the IEEE 754 does not specify byte ordering. At least we can point to {html} <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html#doubleToRawLongBits%28double%29" /> {html} for details.
> - In the resolution section, we should mention how default values for record fields get used
> - There is a sudden mention of "method parameters" in the resolution of records; the reader won't have a clue what it refers to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-85) A few minor errors in and suggestions for
the spec document
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated AVRO-85:
-----------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Thiru.
> A few minor errors in and suggestions for the spec document
> -----------------------------------------------------------
>
> Key: AVRO-85
> URL: https://issues.apache.org/jira/browse/AVRO-85
> Project: Avro
> Issue Type: Bug
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Attachments: AVRO-85.patch
>
>
> There are a few minor errors in the specifications document:
> - The 32-bit and 64-bit floating point numbers should mention the exact IEEE standard (i.e IEEE 754 instead of plain IEEE).
> - It'll be clearer if we state that the long value preceding string or bytes is the number of bytes being encoded.
> - In the binary serialization example for unicode string "foo" the length 3 will get encoded as 0x06 not 0x0c.
> - We should be more specific about how one serializes float and double, Unfortunately, the IEEE 754 does not specify byte ordering. At least we can point to {html} <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html#doubleToRawLongBits%28double%29" /> {html} for details.
> - In the resolution section, we should mention how default values for record fields get used
> - There is a sudden mention of "method parameters" in the resolution of records; the reader won't have a clue what it refers to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-85) A few minor errors in and suggestions for
the spec document
Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiruvalluvan M. G. updated AVRO-85:
------------------------------------
Status: Patch Available (was: Open)
> A few minor errors in and suggestions for the spec document
> -----------------------------------------------------------
>
> Key: AVRO-85
> URL: https://issues.apache.org/jira/browse/AVRO-85
> Project: Avro
> Issue Type: Bug
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
> Attachments: AVRO-85.patch
>
>
> There are a few minor errors in the specifications document:
> - The 32-bit and 64-bit floating point numbers should mention the exact IEEE standard (i.e IEEE 754 instead of plain IEEE).
> - It'll be clearer if we state that the long value preceding string or bytes is the number of bytes being encoded.
> - In the binary serialization example for unicode string "foo" the length 3 will get encoded as 0x06 not 0x0c.
> - We should be more specific about how one serializes float and double, Unfortunately, the IEEE 754 does not specify byte ordering. At least we can point to {html} <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html#doubleToRawLongBits%28double%29" /> {html} for details.
> - In the resolution section, we should mention how default values for record fields get used
> - There is a sudden mention of "method parameters" in the resolution of records; the reader won't have a clue what it refers to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AVRO-85) A few minor errors in and suggestions
for the spec document
Posted by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thiruvalluvan M. G. reassigned AVRO-85:
---------------------------------------
Assignee: Thiruvalluvan M. G.
> A few minor errors in and suggestions for the spec document
> -----------------------------------------------------------
>
> Key: AVRO-85
> URL: https://issues.apache.org/jira/browse/AVRO-85
> Project: Avro
> Issue Type: Bug
> Reporter: Thiruvalluvan M. G.
> Assignee: Thiruvalluvan M. G.
>
> There are a few minor errors in the specifications document:
> - The 32-bit and 64-bit floating point numbers should mention the exact IEEE standard (i.e IEEE 754 instead of plain IEEE).
> - It'll be clearer if we state that the long value preceding string or bytes is the number of bytes being encoded.
> - In the binary serialization example for unicode string "foo" the length 3 will get encoded as 0x06 not 0x0c.
> - We should be more specific about how one serializes float and double, Unfortunately, the IEEE 754 does not specify byte ordering. At least we can point to {html} <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/lang/Double.html#doubleToRawLongBits%28double%29" /> {html} for details.
> - In the resolution section, we should mention how default values for record fields get used
> - There is a sudden mention of "method parameters" in the resolution of records; the reader won't have a clue what it refers to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.