I guess I put the solution before the problem, but basically where I want to
get to is to allow people to write protostream marshallers without requiring
them to write the proto file. This would mean the same effort for java users to
write either JBMAR marshallers or proto marshallers. If
In my experience people express a bit of confusion on their first
impact with our query/indexing technology as there is a strong
conceptual difference compared to the more familiar relational
databases.
The primary WTF effect is usually on the fact that when a field
included in a query is not
Hi everybody,
last week I developed a simple application using Remote Query, and ran
into a few issues. Some of them are just technical hurdles, while others
have to do with the complexity of the developer experience. Here they
are for open discussion:
- the schemas registry should be
On Feb 10, 2014, at 4:54 PM, Tristan Tarrant ttarr...@redhat.com wrote:
- since remote query is already imbued with JPA in some form, an
interesting project would be to implement a JPA annotation processor
which can produce a set of ProtoBuf schemas from JPA-annotated classes.
- on top of
On Mon 2014-02-10 17:54, Tristan Tarrant wrote:
Hi everybody,
last week I developed a simple application using Remote Query, and ran
into a few issues. Some of them are just technical hurdles, while others
have to do with the complexity of the developer experience. Here they
are for open
The idea of auto-generating protobuf schemas based on the marshaller
code was briefly mentioned last time we met in Palma. I would not
qualify it as impossible to implement, but it would certainly be hacky
and leads to more trouble than it's worth.
A lot of info is missing from the marshaller
Most of this is in jira already, so it would be good to comment there.
#1 = ISPN-3747 ISPN-3926
#2 = ISPN-3480 (wording is not the same, but it's the same issue)
#3 = ISPN-3718
#4 =
On 02/10/2014 06:54 PM, Tristan Tarrant wrote:
Hi everybody,
last week I developed a simple application
