>
> Sorry, I can see how that was confusing. I would use the logical type to
> determine the transform, but wouldn't require the user to have configured a
> conversion for the type, which is optional. Basically, I'm saying that this
> feature would support decimal, date, time, and timestamp from st
On Fri, Oct 20, 2017 at 12:13 AM, Bridger Howell wrote:
> But then would I end up with a few bits of ugliness:
> - the schemas have to be wrapped in a made-up protocol
> - the generated code includes a generated protocol class I wouldn't care
> about
>
Wouldn't these be eliminated if we simply p
> So if I understand correctly, you support the idea of human-readable
defaults but not logical-type-dependent interpretation. I don't see how we
could achieve the first without the second, since different logical types
have different human-readable representations. So it seems that the
optional na
[
https://issues.apache.org/jira/browse/AVRO-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212662#comment-16212662
]
Victor Danilchenko commented on AVRO-2098:
--
Great idea, please bump this up a prio
[
https://issues.apache.org/jira/browse/AVRO-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Stowe updated AVRO-2098:
Description:
The Microsoft Azure environment supports saving Apache Avro files from an Event
Hub via
[
https://issues.apache.org/jira/browse/AVRO-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Stowe updated AVRO-2098:
Description:
The Microsoft Azure environment supports saving Apache Avro files from an Event
Hub via
[
https://issues.apache.org/jira/browse/AVRO-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Stowe updated AVRO-2098:
Description:
The Microsoft Azure environment supports saving Apache Avro files from an Event
Hub via
Matthew Stowe created AVRO-2098:
---
Summary: Avro OCF support for non-seekable stream.
Key: AVRO-2098
URL: https://issues.apache.org/jira/browse/AVRO-2098
Project: Avro
Issue Type: New Feature
On Fri, Oct 20, 2017 at 2:04 AM, Frédéric SOUCHU <
frederic.sou...@ingenico.com> wrote:
> In line with Philip Zeyliger on IDL being a good tool for a human to
> produce schema.
> Key features (IMHO):
> - support for includes (killer feature)
> - simpler syntax (a *lot* less '{' and '['...)
> - sim
[
https://issues.apache.org/jira/browse/AVRO-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212536#comment-16212536
]
Nandor Kollar commented on AVRO-1827:
-
Took a look at the latest patch, looks good to m
In line with Philip Zeyliger on IDL being a good tool for a human to produce
schema.
Key features (IMHO):
- support for includes (killer feature)
- simpler syntax (a *lot* less '{' and '['...)
- simpler comments syntax
I have a toolchain going from IDL to Java + C# classes that wouldn't work using
On Thu, Oct 19, 2017 at 9:17 PM, Philip Zeyliger
wrote:
> I'm shaky on the details here, but shouldn't humans be using the *.avdl
> form of specifying schemas?
Maybe.
As it is, I've seen a good number of open projects that work rely on JSON
schemas (.avsc files).
IDL is really more tailored t
12 matches
Mail list logo
