[Hibernate-JIRA] Created: (HSEARCH-836) Evaluate the need to send the writing schema over with the message
7:22 a.m.
Evaluate the need to send the writing schema over with the message
------------------------------------------------------------------
Key: HSEARCH-836
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836
Project: Hibernate Search
Issue Type: Bug
Components: serialization
Affects Versions: 4.0
Reporter: Emmanuel Bernard
Avro knows to read a message serialized by a different writer assuming certain conditions
described in their spec http://avro.apache.org/docs/1.5.1/spec.html
But both reader and writer schema should be provided up deserialization
GenericDatumReader(Schema writer, Schema reader, GenericData data)
Should we embed the schema with each message? It looks like a significant payload.
If we don't, we can use the major.minor version numbers that are before the avro
stream. But that will only work if the receiver is more recent that the writer.
In all case, we need a prototype to test backward compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:22 a.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-836) Evaluate the need to send the writing schema over with the message
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836?pag...
]
Emmanuel Bernard commented on HSEARCH-836:
------------------------------------------
note I've set the community flag up. It is a significant work but that's almost
unrelated to HSearch codebase. It's more related to Avro.
Evaluate the need to send the writing schema over with the message
------------------------------------------------------------------
Key: HSEARCH-836
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836
Project: Hibernate Search
Issue Type: Bug
Components: serialization
Affects Versions: 4.0
Reporter: Emmanuel Bernard
Avro knows to read a message serialized by a different writer assuming certain conditions
described in their spec http://avro.apache.org/docs/1.5.1/spec.html
But both reader and writer schema should be provided up deserialization
GenericDatumReader(Schema writer, Schema reader, GenericData data)
Should we embed the schema with each message? It looks like a significant payload.
If we don't, we can use the major.minor version numbers that are before the avro
stream. But that will only work if the receiver is more recent that the writer.
In all case, we need a prototype to test backward compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 p.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-836) Evaluate the need to send the writing schema over with the message
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836?pag...
]
Sanne Grinovero commented on HSEARCH-836:
-----------------------------------------
I'm wondering if we could send it optionally, this would need some way for the server
to answer with a "I need the schema".
We could have it send the schema once when the backend starts up, but this doesn't
help if the master is restarted; it would be good if the master could store it in it's
local filesystem.
Could an "availables schema store" be shared? A database table, an Infinispan
entry, a jar containing resources to make an old version "forward compatible" to
be deployed on the master.
These look complex, a simple alternative could be to send it periodically every N
messages, where N can be 1 (all), 0 (never) or another positive number. If this was JMX
configurable, admins could force it to send an updated schema to masters when they need.
Even simpler: we support it only on demand (the "I need the schema" request from
the server), and in the JMS case in which we can't answer people will have to upgrade
the master first.
Evaluate the need to send the writing schema over with the message
------------------------------------------------------------------
Key: HSEARCH-836
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836
Project: Hibernate Search
Issue Type: Bug
Components: serialization
Affects Versions: 4.0
Reporter: Emmanuel Bernard
Avro knows to read a message serialized by a different writer assuming certain conditions
described in their spec http://avro.apache.org/docs/1.5.1/spec.html
But both reader and writer schema should be provided up deserialization
GenericDatumReader(Schema writer, Schema reader, GenericData data)
Should we embed the schema with each message? It looks like a significant payload.
If we don't, we can use the major.minor version numbers that are before the avro
stream. But that will only work if the receiver is more recent that the writer.
In all case, we need a prototype to test backward compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
New subject: [Hibernate-JIRA] Commented: (HSEARCH-836) Evaluate the need to send the writing schema over with the message
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836?pag...
]
Emmanuel Bernard commented on HSEARCH-836:
------------------------------------------
This issue is being folded in HSEARCH-880
Evaluate the need to send the writing schema over with the message
------------------------------------------------------------------
Key: HSEARCH-836
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836
Project: Hibernate Search
Issue Type: Bug
Components: serialization
Affects Versions: 4.0
Reporter: Emmanuel Bernard
Avro knows to read a message serialized by a different writer assuming certain conditions
described in their spec http://avro.apache.org/docs/1.5.1/spec.html
But both reader and writer schema should be provided up deserialization
GenericDatumReader(Schema writer, Schema reader, GenericData data)
Should we embed the schema with each message? It looks like a significant payload.
If we don't, we can use the major.minor version numbers that are before the avro
stream. But that will only work if the receiver is more recent that the writer.
In all case, we need a prototype to test backward compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:27 a.m.
New subject: [Hibernate-JIRA] Resolved: (HSEARCH-836) Evaluate the need to send the writing schema over with the message
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836?pag...
]
Emmanuel Bernard resolved HSEARCH-836.
--------------------------------------
Resolution: Out of Date
Evaluate the need to send the writing schema over with the message
------------------------------------------------------------------
Key: HSEARCH-836
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-836
Project: Hibernate Search
Issue Type: Bug
Components: serialization
Affects Versions: 4.0
Reporter: Emmanuel Bernard
Avro knows to read a message serialized by a different writer assuming certain conditions
described in their spec http://avro.apache.org/docs/1.5.1/spec.html
But both reader and writer schema should be provided up deserialization
GenericDatumReader(Schema writer, Schema reader, GenericData data)
Should we embed the schema with each message? It looks like a significant payload.
If we don't, we can use the major.minor version numbers that are before the avro
stream. But that will only work if the receiver is more recent that the writer.
In all case, we need a prototype to test backward compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4803
days inactive
4823
days old
hibernate-issues@lists.jboss.org
4 comments
2 participants
participants (2)
-
Emmanuel Bernard (JIRA) -
Sanne Grinovero (JIRA)