Re: [DISCUSS] Inconsistent behaviour on types as invalid names

low any name that isn't a type _reference_. This means names like string, int, null, float, etc. are not allowed, but date, time_ms, record, union, etc. are. Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: [DISCUSS] Inconsistent behaviour on types as invalid names

RECORD type). Are we allowed to add arbitrary JSON properties > to a type reference? > No: that would either change the named type, or create a copy with changes (and redefining a named type differently is not allowed). Kind regards, Oscar -- Oscar Westra van Holthe - Kind >

Re: [DISCUSS] Inconsistent behaviour on types as invalid names

Oscar Westra van Holthe - Kind On th 10 feb. 2022 22:03, Martin Grigorov wrote: > On Thu, Feb 10, 2022 at 10:47 PM Ryan Skraba wrote: > > > I created https://github.com/apache/avro/pull/1533 to show the impact > > on the Python SDK, if we were to follow the "pe

Re: [DISCUSS] Inconsistent behaviour on types as invalid names

entence; the rest looks great. Thank you! Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Request for comments: new parsing & formatting interface

SchemaFormatter and ProtocolFormatter interfaces Which option do you prefer? Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

A note on Service Provider Interfaces (SPI) WAS: Re: Request for comments: new parsing & formatting interface

g. the Maven plugin. Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

Re: [DISCUSS] Doing a Release 1.11.1?

ttps://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.1%20AND%20status%3DResolved > [2]: > https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.1%20AND%20status!%3D%20Resolved > -- ✉️ Oscar Westra van Holthe - Kind

Re: [ANNOUNCE] New committer: Zoltan Csizmadia

Congratulations Zoltan! Oscar Westra van Holthe - Kind Op di 29 mrt. 2022 15:14 schreef Ryan Skraba : > Hello everyone, > > The Project Management Committee (PMC) for Apache Avro has invited > Zoltan Csizmadia to become a committer and we are pleased to announce > that

Re: AVRO-3408 Schema evolution with logical types

ards compatible. This change introduces a natural/human format for the decimal type (though inefficient in size). As it both adds convenience and is backwards compatible, it has my vote. Kind regards, Oscar Oscar Westra van Holthe - Kind Op wo 30 mrt. 2022 06:30 schreef Micah Kornfield : >

Re: Duration spec change

need milliseconds. But they do need months and days. Although translating the Avro type to a specific language may be tricky (Avro durations support more values than Java intervals and periods, for example), I think it's best to keep it as is. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op

Re: Supporting unicode named fields

: it does support unicode (in the form of Java identifiers). The downside of this though, is that it is inherently unportable and likely not interoperable with other languages. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op wo 4 mei 2022 00:06 schreef Nilesh Yadav : > Hello, >

Re: Supporting unicode named fields

n eye on. Kind regards, Oscar [1] https://github.com/apache/avro/pull/1588 [2] https://github.com/apache/avro/pull/1589 -- Oscar Westra van Holthe - Kind

Re: [DISCUSS] Doing a Release 1.11.1?

Hi, I'd also like to help/shadow, as the release contains a feature that would help me a lot. Also, the sooner we have a release, the sooner the new ANTLR grammar for the 1.12 release can be tested with more than just the test cases. Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: [DISCUSS] Doing a Release 1.11.1?

For me, after 19:00 or Mon,Tue,Thu,Fri between 7:30-16:00 (all UTC) Oscar Westra van Holthe - Kind Op wo 11 mei 2022 10:00 schreef Martin Grigorov : > Hi, > > Me too! > > Now I guess it will be harder to find a timeslot where all of us could do > it :-) > I could find ti

Re: [jira] [Updated] (AVRO-3512) aliases to the null namespace do not work as expected

quot;AncientEnum", > > "symbols" : [ "THE", "SPEC", "IS", "A", "LIE" ] > > } > > } > > ] > > } > > {code} > > and reader schema: > > {code:json} > > { > > "type": "record", > > "namespace": "much.namespace", > > "name": "ModernRecord", > > "fields": [ > > { > > "name" : "enumField", > > "type" : { > > "type" : "enum", > > "name" : "ModernEnum", > > "symbols" : [ "THE", "SPEC", "IS", "A", "LIE" ], > > "aliases": [ > >".AncientEnum" > > ] > > } > > ], > > "aliases": [ > > ".AncientSchema" > > ] > > } > > {code} > > notice the dots used in the aliases. as far as i understand the spec > this should be the only legal way to do this. and it does indeed work > to a point. > > > > when testing this i found multiple issues with avro's handling of such > aliases, dating back to late avro 1.7.* > > > > # without these aliases, decoding does fail, but it fails over the > nested enum, whereas it should have failed "immediately" on the fullname > mismatch on the top level record schema. in fact, on further testing i > think avro (at least in java) doesnt bother comparing the fullnames on the > top level writer vs reader schemas at all? > > # while the schema with the aliases parse()es fine, Schema.toString() > strips out the dots from the aliases, thereby creating a "monsanto > terminator schema" - once printed and parsed again the aliases would become > "simple aliases" and stop working > > # the spec doesnt explicitly talk about how to use aliases to "target" > the null namespace. if this is an intentional feature I think the spec > should be expanded a little to cover it? > > > > i have code to reproduce all these issues in [ > https://github.com/radai-rosenblatt/avro/blob/aliasing-to-null-namespace/lang/java/avro/src/test/java/org/apache/avro/TestAliasToNullNamespace.java] > (coded against master) > > > > i also have code to reproduce all the above against multiple older avro > versions in [ > https://github.com/linkedin/avro-util/blob/master/helper/tests/helper-tests-allavro/src/test/java/com/linkedin/avroutil1/compatibility/AvroTypeAliasesTest.java > ] > > > > -- > This message was sent by Atlassian Jira > (v8.20.7#820007) > -- ✉️ Oscar Westra van Holthe - Kind

Re: [DISCUSS] Drop Hadoop 2 support from Avro

ns of Avro... Does anybody have any objections to > removing Hadoop 2 support in the next major version? > > All my best, Ryan > -- ✉️ Oscar Westra van Holthe - Kind

Re: [DISCUSS] Changing the Avro logo

Hi, Oscar Westra van Holthe - Kind Op wo 22 jun. 2022 21:29 schreef Ryan Skraba : > Hello all! > > Even if our current logo is a nice homage, there are many, many > advantages to using original art for a project logo, and it's > important that there's no questio

Re: [DISCUSS] Changing the Avro logo

es of detail in the wings (for various sizes). As for ideas, mixing aviation with data flow usually gives you a mix of wings and a wave. But there are already many logos in that theme... These are my 2ct.. Oscar Westra van Holthe - Kind Op wo 22 jun. 2022 21:29 schreef Ryan Skraba : > H

Re: [DISCUSS] Changing the Avro logo

gt; > > > On Thu, Jun 23, 2022 at 10:16 AM Oscar Westra van Holthe - Kind > > > wrote: > > > > > > > > Hi, > > > > > > > > To change the logo, I propose we gather both requirements and ideas. > > > > > > > > F

Re: [VOTE] Release Apache Avro 1.11.1 RC1

, July 29th, 2022. > > > > [ ] +1 Release this as Apache Avro 1.11.0 > > [ ] +0 > > [ ] -1 Do not release this because... > > > > Best regards, > > Ryan Skraba > > > > [Countdown to vote]: > > https://www.timeanddate.com/countdown/to?iso=20220729T2359&p0=1440 > > > -- ✉️ Oscar Westra van Holthe - Kind

Re: Re: Impossible to refer to names in the default namespace from another namespace?

ma authors more visible, I'd opt to choose the Java route and in that case force all schemata to belong to a group. I.e., explicitly disallow identifiers to start with a dot (and disallow references to the null namespace from within another namespace). Kind regards, Oscar -- Oscar Westra va

Re: [DISCUSS] Pull request template changes

Thank you Ryan! This version looks much more friendly. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op do 1 sep. 2022 22:48 schreef Martin Grigorov : > Hi, > > +1 for the improvements! > > I hope that less people will ignore it now after explicitly stating that if &g

Re: [DISCUSS] Redirect more JIRA notifications to iss...@avro.apache.org

Hi all, Personally, i delete many notification mails because I'm not interested. Needing to subscribe to the ones I do find interesting is not a hassle and would make discussions more visible. So this change is a good one in my opinion. Kind regards, Oscar Oscar Westra van Holthe - Kind

Re: Avro Java Version

cessUnsafe or the new class depends of JDK version with Maven > trick). > > Whole unit tests work fine. > > I wonder if there are other good reasons to stay with Java 8 version. > > > > Best regards, > > Christophe Le Saëc > -- ✉️ Oscar Westra van Holthe - Kind

Re: [ANNOUNCE] New PMC member: Martin Grigorov

Congratulations Martin! This is wel deserved. Oscar Westra van Holthe - Kind Op di 13 sep. 2022 19:34 schreef Ryan Skraba : > Hi folks! > > On behalf of the Apache Avro PMC, I am pleased to announce that Martin > Grigorov has accepted our invitation to become a PMC member.

Re: Don't throw can't redefine error when the schema is identical

. Statements in this message that do not relate to the > > business of Gresham are neither given nor endorsed by the company or its > > directors. Gresham Technologies plc Registered in England and Wales. > > Company No. 01072032 Registered Office: Aldermary House, 10-15 Queen > > Street, London, EC4N 1TX. Further information about Gresham Technologies > > can be found on our website: www.greshamtech.com > > > -- ✉️ Oscar Westra van Holthe - Kind

Re: [VOTE] Accept donation of gradle-avro-plugin

+1 (non-binding) from me FYI: According to this link, the Spring Boot Gradle plugin is built with Maven: https://stackoverflow.com/a/27556212/3169109 Kind regards, Oscar Westra van Holthe - Kind Op ma 10 okt. 2022 18:58 schreef Ryan Skraba : > Hello everyone! > > The developer(s)

Re: New website

Hi, This is a huge improvement. Responsive, excellent navigation, syntax highlighting, ... The only downside I see was already mentioned by Lee: the landing page is too empty (also in a mobile browser). I think we could really benefit from mentioning the unique selling point of Avro here: "Your D

Poll: optional types & union defaults

Hi everyone, In PR #1411 for issue AVRO-3257 , I've added some code to change/fix a union based on its default value. Currently, the change is in idl.jj, line 186-210

Re: Poll: optional types & union defaults

o rewrite the UNION schema. > > All my best -- and it's always worth repeating that I'm appreciating > and learning a lot from your work on the IDL side! > > Ryan > > > > On Fri, Dec 10, 2021 at 7:30 PM Oscar Westra van Holthe - Kind > wrote: > > > &

Re: New committer: Martin Grigorov

t; > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > It's great to have you as part of the team, Martin! > -- ✉️ Oscar Westra van Holthe - Kind

Maintaining the IDL in the 21st century

a Maven plugin, to generate the parser during the build 3. I know where to find working examples Does anyone have a better/easier suggestion? Or should I continue with ANTLR? Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: Maintaining the IDL in the 21st century

yet. I'll add this as a PR shortly. Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

Re: Maintaining the IDL in the 21st century

e Stata > wrote: > > > > I support your recommendation. I've recently used ANTLR on a use-case > > similar to this one and had a great experience. > > > > Raymie > > > > On Wed, Jan 5, 2022 at 5:13 PM Oscar Westra van Holthe - Kind < > &g

Re: [DISCUSS] Releases, versioning and lifecycle

l bug fixes > > 2) only the bug fixes requested by the reporter or other users > > > > Another question: When making a release for a patch version, like 1.10.3, > > you'd release all langs or just the ones having any backports ? I guess > the > > latter because it would reduce the work to cut a release > > > > Regards, > > Martin > > > > > > > All my best, Ryan > > > > > > [1]: https://issues.apache.org/jira/browse/AVRO-2687 "Semantic > versioning" > > > [2]: > > > > https://lists.apache.org/thread.html/16b68748464a7ce7232f12bbbf781cbfd5de982785d5648b6c564cc9%40%3Cdev.avro.apache.org%3E > > > "[DISCUSS] version numbers and where changes should land" > > > [3]: > > > > https://lists.apache.org/thread.html/r9ec7d8801186d3242e6d535adb547ba5068f5a4e0202ec1bd5d8912a%40%3Cdev.avro.apache.org%3E > > > "Proposal: RFCs for Avro 2.x" > > > [4]: https://github.com/apache/avro/pull/1333 "Backport AVRO-3048" > > > > -- ✉️ Oscar Westra van Holthe - Kind

Re: New website

Hi all, +1 from me for moving to the new website You've done a great job! -- Oscar Westra van Holthe - Kind Op di 25 jan. 2022 08:36 schreef Martin Grigorov : > Hi, > > Shall we replace the old website with the new one ? > > I will have time to work on it next week, so

Re: Programming languages for Avro

ce (*Mine would be > to remove perl, php and ruby*). > May be a doodle like system would be a solution (for each language, get pro > & cons; and remove an implementation when there are more than 80% cons). > > WDYT ? > -- ✉️ Oscar Westra van Holthe - Kind

Re: [DISCUSS][VOTE] Naming rules

t;https://github.com/apache/avro/pull/1798>) >2. change the code (in Java and C# at least) to be conformed to >documentation. > For compatibility, I like option 1. If we're to change naming rules, I'd vote for logging warnings before tightening the rules. Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

Re: Programming languages for Avro

Oscar Westra van Holthe - Kind On thu 10 nov. 2022, 19:32 Ryan Skraba wrote: > I actually met some people from the French perl Mongueurs yesterday! > They're still going strong (http://mongueurs.pm/), and I talked to > some engineers from a big music streaming platform still bas

IDL schema parsing for the 21st century

criticism :) Kind regards, Oscar Oscar Westra van Holthe - Kind

Re: IDL schema parsing for the 21st century

s, PR 2 - 113, PR 3 - 251) ! > I'll let someone else who knows better the Java code to review them. I'm > afraid I can't help much here. > > Martin > > On Tue, Nov 15, 2022 at 3:08 PM Martin Grigorov > wrote: > > > Hi Oscar, > > > > I will try to

Re: Release language modules separately

rsioning scheme: spec.major.minor, where the spec version denotes compatibility of the binary format and parsing canonical form. That makes it possible to at least have some idea about interoperability without consulting a lookup table. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op di 3

Re: Release language modules separately

ind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

Re: Release language modules separately

res" table is then one to pick up quickly after we implement our choice. Anyway, that's my opinion on the matter. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op vr 13 jan. 2023 09:31 schreef Christophe Le Saëc : > Indeed, "Commons tests" embeds avro files that a

Re: [DISCUSS] Java 8 compatibility?

e already use dependencies that require that higher Java version. It is a very user friendly way to (partially) drop Java 8 support. Another question: if we target Java >8 for a module, should that use the Java Module system as well? Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op

Re: [DISCUSS] Release Avro 1.11.2

Python/Rust/... Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: [JAVA] Proposal: Dropping theUnsafe

onger use the > "matrix" build and will build the project only once (I expect it to > become faster because of that). > > Your opinions on this? > > -- > Best regards / Met vriendelijke groeten, > > Niels Basjes > -- ✉️ Oscar Westra van Holthe - Kind

Re: [VOTE] Release Apache Avro 1.11.2 RC1

> > https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.2 > > > > > > I'll send a follow-up email with the notable highlights for each > > > language and SDK, but I wanted to give everyone a head start to > > > check their favourite fixed JIRAs and features! > > > > > > Please download, verify, and test. This vote will remain open for at > > least > > > 72 hours. I would like to close at 11h59 UTC Friday, June 30th, 2023 > > > > > > [ ] +1 Release this as Apache Avro 1.11.0 > > > > > > > Typo: it should be 1.11.2 > > > > > > > > > [ ] +0 > > > [ ] -1 Do not release this because... > > > > > > Best regards, > > > Ryan Skraba > > > [Countdown to vote]: > > > https://www.timeanddate.com/countdown/to?iso=20230630T1159&p0=1440 > > > > > > -- ✉️ Oscar Westra van Holthe - Kind

Re: [DISCUSS] Release maintenance and lifecycle

, and not all at once? One question though: do we keep the releases bundled with all languages? Or do we also want to split that? (I'd like to keep them bundled). Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op di 1 aug. 2023 20:12 schreef Ryan Skraba : > Bringing this subje

Re: Enum default not in canonical form

perties in the canonical form, or to determine if the properties allow resolution. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op ma 31 jul. 2023 19:42 schreef Ryan Skraba : > This is a bit weird, and it could be clarified. > > The "same" schema, of course, can be

Re: Generated code breaking change

; > So, is it acceptable changes considering it only occurs in case of name > conflict ? > As I have not encountered such naming collisions other than in very small numbers, so I think it's perfectly acceptable. Does anyone have different experiences? Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

Re: Specification of namespaces

.org/jira/browse/AVRO-3833> (with PR <https://github.com/apache/avro/pull/2448>) because I wanted to clarify that names must be unique (because otherwise schema resolution cannot work), and that this includes aliases. The change also includes this migration/fix option. Kind regards, Os

Re: Specification of namespaces

rocess to do other nice things: - skip written fields that were removed from the read schema - fill in default values for new fields added to the read schema - match different type orders in unions - do some conversions, like reading an int as a long Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

[DISCUSS] Changing the Avro logo (revisited)

, and indicate which ones we like best? We can then pick the most mentioned versions, and call a vote. Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Re: New Big Decimal Logical type

ample, cannot convert the Avro value. So in all honesty, I think marking it as experimental is not needed. But I think we should, because marking new logical types as experimental allows the option to abandon it later on. Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind

Re: [DISCUSS] Release maintenance and lifecycle

ecome easier. Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: New Big Decimal Logical type

don't want that. I would however, like to see a way to do schema evolution on logical types. That would allow (for example) widening conversions on decimals, same as for int/float now. Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Re: Specification of namespaces

anks again, > Michael > > On Fri, Aug 18, 2023 at 03:17 Oscar Westra van Holthe - Kind < > os...@westravanholthe.nl> wrote: > > > On Fri, 18 Aug 2023 at 04:32, Michael A. Smith > > wrote: > > > > > I found I'm still a little confused at how usin

[VOTE] New Avro logo

two (2) votes more than the runner-up - if there is no clear winner, we'll vote by simple majority between the top picks Please vote for your preference! Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Re: [VOTE] New Avro logo

Hi all, Since the start, I've been a fan of the pigeon. It looks good, and it's very distinctive. And it's completely different from any send icon, so it cannot be conflated with a message protocol icon. My vote is for V3.1 Kind regards, Oscar -- ✉️ Oscar Westra van Holthe -

Re: [VOTE] New Avro logo (final)

t with these current logos and leaving > any changes to Emma's discretion! > > All my bets Ryan > > On Mon, Oct 2, 2023, 13:08 Ryan Blue wrote: > > > My vote is for 10.2. > > > > On Mon, Oct 2, 2023 at 9:02 AM Oscar Westra van Holthe - Kind < > > os...

Re: [VOTE] New Avro logo (final)

an example of this, think of Apple's logo, which is a > simplistic apple icon with a chunk missing. I would posit that if Apple > wrote 'Apple' on their icon, it wouldn't be nearly as effective. > > That's my 2¢ anyways! I'm happy to make more adjustments to t

Re: [VOTE] New Avro logo (final)

gt; > revisions for the font used in the final design (once a winner is > > > chosen) > > > > > to see if there is a better alternative on that front, but > otherwise, > > > the > > > > > icon designs themselves will remain the same. Thanks again for

Re: [VOTE] New Avro logo (final)

kt 2023 om 07:39 schreef Daniel Kulp : > > > > > v9.2 for me. I definitely prefer the blue color and I really don’t get > > the pigeon. > > > > Dan > > > > > > > On Oct 23, 2023, at 5:04 AM, Oscar Westra van Holthe - Kind < > > os...@westr

Re: [VOTE] New Avro logo (final)

Hi all, On a related note, I'd also like to use the final logo as plugin icon and as (part of the) file icon in the JetBrains Pugin I maintain. Are there any objections to that? Kind regards, Oscar -- Oscar Westra van Holthe - Kind On Fr 27 oct 2023 18:17, Ryan Skraba wrote:

Re: [VOTE] New Avro logo (final)

amp; without text that work on backgrounds of #2b2d30 and #f7f8fa (not quite black and white), and #30638e (the current website blue)? Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Help wanted: 2nd test in ARM64 build fails

d to be different from the code being used? Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Re: Help wanted: 2nd test in ARM64 build fails

-- Oscar Westra van Holthe - Kind On fr 10 nov. 2023 14:04, Martin Grigorov wrote: > I've ignored the avro-ipc-jetty Maven module and the build passed! > > I also re-triggered the build on main ( > https://github.com/apache/avro/actions/runs/6784706838/job/18554971516) >

Re: Hyphens in Avro schema namespaces and the rust deserializer

op\",\"type\":\"string\"},{\"name\":\"ts_ms\",\"type\":[\"null\",\"long\"],\"default\":null},{\"name\":\"transaction\",\"type\":[\"null\",{\"type\":\"record\",\"name\":\"block\",\"namespace\":\"event\",\"fields\":[{\"name\":\"id\",\"type\":\"string\"},{\"name\":\"total_order\",\"type\":\"long\"},{\"name\":\"data_collection_order\",\"type\":\"long\"}],\"connect.version\":1,\" > > connect.name > > \":\"event.block\"}],\"default\":null}],\"connect.version\":1,\" > > connect.name > \":\"debezium.abc-123-efg-20231005.table.u_table_dbz.Envelope\"}" > > cant be turned into a Schema, was cause by Invalid namespace > > debezium.abc-123-efg-20231005.table.u_table_dbz. It must match the regex > > '^([A-Za-z_][A-Za-z0-9_]*(\.[A-Za-z_][A-Za-z0-9_]*)*)?$', it's retriable: > > false, it's cached: false > > ``` > > > > Ideally, the Avro spec would just accept hyphens since they’re a pretty > > common character and unavoidable in certain circumstances. If this is > > easier said than done, I think at the least any library used for Avro > > deserialization should account for them, including the rust library. If > > this works in Java and Python, shouldn’t it also work in rust? > > > > This is exactly the reason I asked you to raise this question here in the > mailing list! > I also agree that if most/all of the SDKs will allow hyphens in the > name[space] then it is a better idea to add it to the list of allowed > characters in the specification instead of adding logic to disable the > validation. > > @Avro devs: What is your opinion ? > > Martin > > > > > > Here’s a generic example of a schema created by a Debezium connector: > > > > ``` > > { > > "type": "record", > > "name": "Envelope", > > "namespace": "abc-123-efg-20231005.table.u_table_dbz", > > "fields": [ > > { > > "name": "before", > > "type": [ > > "null", > > { > > ... > > ``` > > > > Please let me know if you need any more details, and thank you! > > > > Jon Slusher > > > > > > > > > -- ✉️ Oscar Westra van Holthe - Kind

New project logo

Hello everyone, As we've recently completed our search for a new logo, I've taken the liberty to open a PR to put the new logo on the website: https://github.com/apache/avro/pull/2594 In addition to this, we should update the logo here: https://www.apache.org/logos/ I've added a new Jira issue f

Re: [DISCUSS] Apache Avro 1.12.0

Good idea. I would really like to include the changes necessary to complete AVRO-3666 (the new SchemaParser class). Ideally, I'd also like to include a counterpart for formatting schemas, by that can also wait until 1.12.1. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op di 1

Re: [VOTE][LAZY] Support for UUIDs encoded as Fixed[16]

+1 for UUIDs encoded as fixed from me as well. A already remarked, an automatic conversion from strings would be very helpful. However, this has a big influence on schema resolution and should be dealt with separately. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op di 23 jan. 2024

Re: Avro query on Testing if Beta feature of Generating faster code is enabled

, Oscar -- Oscar Westra van Holthe - Kind Op di 6 feb. 2024 07:15 schreef chirag : > Hi Team, > > On the Avro Docs it is mentioned that:- to turn new approach to generating > code that speeds up decoding and encoding set feature flag/system flag > org.apache.avro.specific.use_c

Re: [DISCUSS] Apache Avro 1.12.0

enforces this, and thus ensures no invalid schemata can be returned. I’ll make a new PR, a subset of #2642 <https://github.com/apache/avro/pull/2642>, to include just that. Kind regards, Oscar -- Oscar Westra van Holthe - Kind > On 12 Feb 2024, at 22:53, Fokko Driesprong wrot

Re: Python Wheels

Hi, +1 on releasing a wheel for 1.11 3. On pypi.org, I see we did publish our releases. Would it be much trouble to ensure we've published a wheel for all of them? Or does that not make sense? Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op do 29 feb. 2024 01:04 schreef Mi

Re: [PROPOSAL] Apache Avro 1.11.4 release

Hi everyone, As I remember the discussion, we'd support both the last major release and the current one. This would mean we should release both 1.11.4 and 1.12.0. Did I remember correctly? Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op vr 5 apr. 2024 17:20 schreef Ryan S

Re: Volunteering for Avro 1.11.4 and 1.12.0 releases

+1 -- Oscar Westra van Holthe - Kind Op di 16 apr. 2024 10:55 schreef Martin Grigorov : > On Tue, 16 Apr 2024 at 11:21, Jean-Baptiste Onofré > wrote: > > > Hi Martin, > > > > (finally I received the email from the list cleanly, w00t ;)) > > > > Than

Re: Formal spec for Avro Schema

he binary encoding (warning to never use it directly), Avro files, the Single-Object encoding, protocols, the protocol wire format, and the IDL schema and protocol definitions. Kind regards. Oscar -- Oscar Westra van Holthe - Kind > On 15 May 2024, at 11:17, Clemens Vasters via u

Re: Volunteering for Avro 1.11.4 and 1.12.0 releases

as I have very limited time outside of work at the moment. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op di 25 jun. 2024 07:37 schreef Jean-Baptiste Onofré : > Hi folks > > PR #2934 (https://github.com/apache/avro/pull/2934) has been merged. > > Martin and others also

Re: Volunteering for Avro 1.11.4 and 1.12.0 releases

Thank you! -- Oscar Westra van Holthe - Kind Op di 25 jun. 2024 09:47 schreef Driesprong, Fokko : > Hey Oscar, > > I'm around for some reviews. I left a comment. > > Kind regards, > Fokko > > Op di 25 jun 2024 om 09:30 schreef Oscar Westra van Holthe - Kind

Re: [VOTE] Release Apache Avro 1.12.0

+1 (binding) to release 1.12.0 - Can build from source distribution - Tested with some other projects (avro-conversions, some company projects, …) Kind regards, Oscar -- Oscar Westra van Holthe - Kind > On 26 Jul 2024, at 16:56, Jean-Baptiste Onofré wrote: > > Hi everyone, >

Re: Where's the source code of the "community" page?

vro sources with submodules): doc/themes/docsy/layouts/community/list.html doc/themes/docsy/layouts/partials/community_links.html doc/themes/docsy/i18n/*.toml (search for “# Community") Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: [VOTE] Release Apache Avro 1.12.0

Sorry about that, I misunderstood the docs I think. -- Oscar Westra van Holthe - Kind Op di 30 jul. 2024 19:48 schreef Jean-Baptiste Onofré : > Hi Oscar, > > According to the record, you are committer, not PMC member, so your > vote is non binding. > > We still need one

Re: [DISCUSS] Release Avro Java 1.11.4

I agree with the Java only 1.11.4 release: AFAIK, its the only one that is not fully compatible due to the change in JRE version. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op do 8 aug. 2024 22:24 schreef Martin Grigorov : > +1 to release 1.11.4 for Java only! > Later

Re: Status of AVRO-2078 - enforcement of Avro schema resolution rules for Decimal type? (java)

vro, I'd vote not to merge this. We need to decide on the future shape of the Parsing Canonical Form and schema fingerprints first, to make these types of evolution possible. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op ma 19 aug. 2024 14:25 schreef Katrin Skoglund : > I&

Re: Status of AVRO-2078 - enforcement of Avro schema resolution rules for Decimal type? (java)

. > Thwe are indeed two variations of the same issue. I prefer to tackle them at once, as it really should not be difficult. The most tricky thing is to identify how to work with multiple Avro/PCF versions simultaneously, and document the limits/caveats one needs to take into account. Kind regards, Oscar -- Oscar Westra van Holthe - Kind >

Re: [VOTE] Extract the Rust SDK into its own Git repository

thub Actions workflows would be moved over > to > > >> the > > >> > new repository (probably without their Git history since it is not > > really > > >> > important). They will be updated to checkout the main repo to make > > use of > > >> > the shared/ folder for the common and interop tests. > > >> > > > >> > Maybe a next step could be to invite > > >> > https://github.com/lerouxrgd/rsgen-avro as a member/sub- crate if > the > > >> > author is interested ! > > >> > Some discussion has happened at > > >> > https://github.com/lerouxrgd/rsgen-avro/pull/56 > > >> > > > >> > Regards, > > >> > Martin > > >> > > > >> > > > > -- > > Xuanwo > > > > https://xuanwo.io/ > > > -- Oscar Westra van Holthe - Kind

Re: [VOTE] Extract the Rust SDK into its own Git repository

+1 from me as well -- Oscar Westra van Holthe - Kind Op di 27 aug. 2024 08:40 schreef Renjie Liu : > Thanks for bringing this up! > > +1 from my side. > > On Sat, Aug 24, 2024 at 11:46 AM xxchan wrote: > > > +1 (non-binding). Thanks for bringing this up! > > >

Re: The "aliases" annotation in Avro schemas for Full Compatibility when used in Java.

lps to make it work. Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: [DISCUSS] Drop pypy 3.9 tests for avro python

+1 from me as well. The maintainers argument Martin mentioned is a strong one. Upgrading the Python versions we mention and use in a separate PR is also a good idea. Kind regards, Oscar -- Oscar Westra van Holthe - Kind Op wo 9 okt. 2024 10:08 schreef Martin Grigorov : > Hi, > > I

Re: Block Level Metadata

k access to the last record, or a bit of metadata at the end of the file. To my knowledge, adding min/max data, bloom filters, etc. is about querying efficiently. I mostly see Parquet files being used for this. What are the use cases where Avro files would be better? Kind regards, Oscar -- O

Import order for Java source files

default order imposed by the spotless plugin (two groups, static first, each ordered lexicographically) 2. The same, but sort JDK imports (the java/javax packages) separately in a third group Do you have a preference? Kind regards, Oscar -- Oscar Westra van Holthe - Kind

Re: [VOTE] Release Apache Avro-rs 0.18.0

h/to/0.18.0/avro" } and test your application > > Please download, verify, and test. This vote will remain open for at least > 72 hours. > > [ ] +1 Release this as Apache Avro-rs 0.18.0 > [ ] 0 > [ ] -1 Do not release this because... > > Regards, > Martin > -- ✉️ Oscar Westra van Holthe - Kind

Re: Discuss: add geospatial types to Avro

Hi, >From what I see on the PR you mentioned, is that this would mean (in Avro terms) logical types for geometry & geography (both coordinates)? Do I understand this correctly? Additional things, such as lines, polygons and expressions, fall outside our scope of data representation. Both the geo

Re: Rustdocs on the website. Was: Re: [VOTE] Release Apache Avro-rs 0.18.0

On Tue, 15 Apr 2025 at 14:29, Martin Grigorov wrote: > On Mon, Apr 14, 2025 at 9:19 AM Martin Grigorov > > On Fri, Apr 11, 2025 at 10:58 AM Oscar Westra van Holthe - Kind < > > os...@westravanholthe.nl> wrote: > >>- The documentation is well structured (pity it

Documenting the security model on the Avro Security page

ite new to this sort of documentation, so any tips to improve this are most welcome! Kind regards, Oscar -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Re: Json decoding & resolving without writer's schema

actice. Nevertheless, it > is an interesting observation that this is possible. Appreciated if people > want to double-check the logic. > > Zhong Yu > z...@godaddy.com > -- ✉️ Oscar Westra van Holthe - Kind 🌐 https://github.com/opwvhk/

Re: Ambiguous reference

>> .endRecord()) > >> .noDefault() > >> .endRecord(); > >> final Schema parsed = new Schema.Parser().parse( > >> ambiguous.toString()); > >> // Th

Re: Documenting the security model on the Avro Security page

nless this is clear from the API, nor will we execute random > code. > Although schemas can define custom (implicit) conversions, and execute > foreign > code, this is always controllable by the downstream application. > > > What do you think can be improved? I'm quite new to this sort of > documentation, so any tips to improve this are most welcome! > > > Kind regards, > Oscar > > -- > > ✉️ Oscar Westra van Holthe - Kind 🌐 > https://github.com/opwvhk/ > > > >

Re: [PROPOSAL] Release Avro 1.11.5 and 1.12.1

; > > > > > > I proposed a security improvement in Avro in this PR: > > > > > > https://github.com/apache/avro/pull/3376 > > > > > > > > > > > > I'm proposing to release Avro 1.11.5 and 1.12.1 when #3376 is > merged. > > > > > > > > > > > > If there are no objections, I'm volunteer to do these releases. > > > > > > > > > > > > > > > > +1 > > > > > Thank you, JB! > > > > > > > > > > > > > > > > > > > > > > > > > > > Thoughts ? > > > > > > > > > > > > Regards > > > > > > JB > > > > > > > > > > > > -- ✉️ Oscar Westra van Holthe - Kind

  1   2   3   >