[
https://issues.apache.org/jira/browse/AVRO-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194934#comment-13194934
]
Sam Pullara commented on AVRO-1006:
-----------------------------------
It seems that the protocol for any system, even one using hashes, would have to
follow that same protocol even if the "inserter" also acts as the repository.
The only critical thing is that there is some way to generate a unique
identifier and store a schema with that as the key that can be looked up by any
receiver of the message. Only after that is done can you send a message using
that identifier (and expect it to be understood).
One advantage that using hashes have over my sequence number suggestion is that
you can easily shard, federate and merge hash-based repositories, qualities
that could be useful in practice. Also, looking up a schema by its canonical
text rather than determining its existence in the repository through hash
lookup would likely be more efficient.
> Fingerprints for Avro Schemas
> -----------------------------
>
> Key: AVRO-1006
> URL: https://issues.apache.org/jira/browse/AVRO-1006
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Raymie Stata
> Assignee: Raymie Stata
> Labels: features
> Attachments: schema-fingerprinting.html, schema-fingerprinting.html,
> schema-fingerprinting.html
>
>
> Add function that returns a standardized, 64-bit fingerprint for schemas.
> Fingerprints are designed such that the chances of collisions is very, very
> low.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
