Re: Formal spec for Avro Schema

add a second document that is very similar to the specification but uses a different language style. To me this looks like a duplication. IMO it would be better to suggest (many) (smaller) improvements for the existing document. > > Best Regards > Clemens > > -Original Message-

Re: Formal spec for Avro Schema

Hi Clemens, What is the difference between your document and the specification [1] ? I haven't read it completely but it looks very similar to the specification to me. 1. https://avro.apache.org/docs/1.11.1/specification/ 2.

Re: Volunteering for Avro 1.11.4 and 1.12.0 releases

o :)). > > Thoughts ? +1 > > Regards > JB > > On Tue, Apr 16, 2024 at 9:54 AM Martin Grigorov > wrote: > > > > Hi, > > > > There were few discussions about this some months ago, e.g. > > https://lists.apache.org/thread/bd39zhk655pg

Re: Volunteering for Avro 1.11.4 and 1.12.0 releases

Hi, There were few discussions about this some months ago, e.g. https://lists.apache.org/thread/bd39zhk655pgzfctq763vp3z4xrjpx58 I think everyone agreed that 1.12.0 could be bumped to Java 11+! https://lists.apache.org/thread/b8d7cjywz6mpj81bhbx5tz6flbvwzsdk - here Niels even suggested to bump

Re: Drop support for pypy3.7 and 3.8

+1 On Tue, 16 Apr 2024 at 5:14, Michael A. Smith wrote: > Please note I'm not proposing any changes to our CPython support in > this thread. This is just about pypy. > > The currently active versions of pypy only supports 3.9 and 3.10. I > propose we track whatever the latest pypy supports. > >

Re: Avro website is not up to date with release

Hi, You might be interested in https://github.com/apache/avro/pull/2187 On Wed, Mar 13, 2024 at 7:11 PM Jean-Baptiste Onofré wrote: > Hi folks, > > I just noted that the release mentioned on the website is still 1.11.1 > (not 1.11.3), for documentation, blog, or download page. > > If there are

Re: [PROPOSAL] Apache Avro 1.11.4 release

Hi, On Wed, Mar 13, 2024 at 7:16 PM Jean-Baptiste Onofré wrote: > Hi folks, > > Recently, we upgraded to commons-compress 1.26.0 (on main). > commons-compress 1.26.0 fixes several CVEs (CVE-2024-25710, > CVE-2024-26308, CVE-2023-42503). > > Would it be possible to release Avro 1.11.4 (that will

Re: Python Wheels

HI, I'm +0. I guess it is OK to push wheels retroactively but no one noticed the missing wheels for almost 4 years, so it does not seem urgent too. Martin On Thu, Feb 29, 2024 at 2:04 AM Michael Smith wrote: > It turns out we haven't been publishing Python wheels to pypi.org because > I >

Re: Make Apache Avro a proper Java module.

>>> More and more libraries these days are dropping support for JDK 8 (at > >>> least > >>> Spring Boot 3, Jakarta EE 11, Mockito 5, among others), so I personally > >>> think it would be fine to drop support for JDK 8 in 1.12.0, or maybe > even >

Re: [DISCUSS] Apache Avro 1.12.0

maintenance policy changes (which > >> > versions will be maintained, etc) and other eventual backward > >> incompatible > >> > changes. > >> > > >> > Any volunteer to be the release manager? > >> > > >> &

Re: Make Apache Avro a proper Java module.

nally > >> think it would be fine to drop support for JDK 8 in 1.12.0, or maybe > even > >> bump the Avro release to 2.0.0 with the removal of JDK 8 support? > >> > >> On Mon, Jan 8, 2024 at 2:38 AM Martin Grigorov > >> wrote: > >> > &

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

improvements > before/after? > You can run your favorite profiler with your application. > > sincerely > Chirag Nahata > > On Tue, Feb 6, 2024 at 5:03 PM Martin Grigorov > wrote: > >> >> >> On Tue, Feb 6, 2024 at 1:15 PM Siddharth Baranidharan >>

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

On Tue, Feb 6, 2024 at 1:15 PM Siddharth Baranidharan wrote: > Hey Oscar, > Thank you for your response. > My application is an enterprise server(java based)-agent(python based) > model which uses avro-protocol for communication between server & agents. > To the best of my knowledge I have added

Re: Flaky Github ARM builds

https://issues.apache.org/jira/browse/INFRA-25464 On Fri, Feb 2, 2024 at 10:23 AM Niels Basjes wrote: > Yes, that sounds indeed like a very good approach. > Can you please report this (I don't know where to report this)? > > Niels > > > > On Thu, Feb 1, 2024 at 9:05 PM

Re: Flaky Github ARM builds

Hi, Another option is to report to the Apache Infra team that the ARM64 self-hosted nodes have these communication problems. The ARM64 self-hosted nodes are an experimental feature provided by the Infra team. Any feedback would be welcome! Martin On Thu, Feb 1, 2024 at 5:20 PM Niels Basjes

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

I just want to add that it would be nice to add an interop test, e.g. an Avro file written by one SDK should be readable by the other SDKs. On Fri, Jan 19, 2024 at 11:58 AM Driesprong, Fokko wrote: > Hey everyone, > > Last December I proposed support for encoding UUIDs as fixed[16] >

Re: Avro schema evolution support in AVRO CPP

Hi Vivek, I am not sure there is anyone to give you an exact answer. The C++ SDK has not been actively developed in the last few years. The best is to try it for your use cases and see if it works or not. The next step is to contribute Pull Requests for the missing functionalities! Martin On

Re: Make Apache Avro a proper Java module.

Hi, I think this is a good idea! Some PRs (mostly by dependabot) are not merged because Avro needs to be JDK 8 compatible and the dependencies require a newer JDK... I am not sure whether Avro 1.12.0 still needs to be JDK 8 compatible or not. Martin On Sat, Jan 6, 2024 at 5:55 PM Chad Preisler

Re: [DISCUSS] Extending the UUID logical type with Fixed[16]

Hi, How would the application tell Avro what storage type to use - String or bytes ? - new logical type ? e.g. "logicalType": "uuid-bytes" - extra attribute ? e.g. { ..., "logicalType": "uuid", "storage-type": "bytes" } - global switch that tells the library to always use "string" or "bytes" for

Re: [DISCUSS] Apache Avro 1.12.0

+1 to release 1.12.0 ! BTW there were few other discussions at dev@ about how many branches to maintain once 1.12.0 is released, for how long, etc. I think this is also an important topic to conclude on! Regards, Martin On Tue, Dec 12, 2023 at 11:21 AM Fokko Driesprong wrote: > Hi everyone, >

Re: [External Sender] Re: Converting from Parquet -> Decimal Type Failure

verter converter = new AvroSchemaConverter(configuration); > Schema schema = converter.convert(messageType); > > Best, > > Salim Memon > Cell: (832) 314 5518 > > > > On Tue, Dec 12, 2023 at 3:00 AM Martin Grigorov > wrote: > >> Hi Salim, >> >>

Re: Converting from Parquet -> Decimal Type Failure

Hi Salim, Could you please give more details about the Avro tool/library you use ? I have the feeling you use some third party library that is not supported by the Apache Avro team. Martin On Mon, Dec 11, 2023 at 9:47 PM Salim Memon wrote: > Hi Devs, > > We are currently running into an issue

Re: Hyphens in Avro schema namespaces and the rust deserializer

; Specifically, I think we should only add to the spec to allow words of > alphanumeric characters, optionally in snake or kebab case. In a regular > expression, this would mean: [a-zA-Z][0-9a-zA-Z_-]*[0-9a-zA-Z]? > +1 I like the new regex! Martin > > Kind regards, > Oscar &g

Re: Hyphens in Avro schema namespaces and the rust deserializer

Hi Jon, Thank you for this email! On Mon, Nov 13, 2023 at 7:56 PM Jonathan Slusher wrote: > Hi, > > I opened an issue in the AVRO project in Jira < > https://issues.apache.org/jira/browse/AVRO-3900> and I’ve been asked to > submit a topic for discussion to this email group. > > See this issue

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

ignore it for now! On Fri, Nov 10, 2023 at 2:56 PM Martin Grigorov wrote: > [INFO] Results: > [INFO] > [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > [INFO] > > [INFO] Reactor Summary

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

ot;, family: "unix" On Thu, Nov 9, 2023 at 8:39 PM Martin Grigorov wrote: > Hi Oscar, > > Deleting the Github Actions cache didn't help! > > Here are the differences I see: > - The AMD64 workflow executes "./build.sh test" while the ARM64 one: > "./b

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

Hi Oscar, Deleting the Github Actions cache didn't help! Here are the differences I see: - The AMD64 workflow executes "./build.sh test" while the ARM64 one: "./build.sh clean test". I doubt that the "clean" breaks it - The ARM64 test uses Maven 3.9.4, while the AMD64 one - 3.8.8 and prints this

Re: [rust] Better support for union schema (patch included)

Hi Simon, Yes, we are interested in any and all kinds of improvements! Please create a JIRA issue and send a Pull Request with the diff above! Thank you! Martin On Sat, Nov 4, 2023 at 3:25 AM Simon Gittins wrote: > Hello > > I've written some failing rust unit tests showing: > - Non trivial

Re: [rust crate apache_avro] Alias and Serde Serialization

Hi Josua, You can see our complete discussion at https://lists.apache.org/thread/jtx7520hq2bd98ksqsbg2nll94htjf40 There is a "Subscribe to list" button on the left side of https://lists.apache.org/list.html?dev@avro.apache.org Thank you for the test case! I've added it to the test suite!

Re: [rust crate apache_avro] Alias and Serde Serialization

Hi Josua, I just realized that you are not subscribed to the mailing list and you didn't receive my earlier responses. Please see below. Martin On Tue, Oct 24, 2023 at 11:41 AM Martin Grigorov wrote: > https://issues.apache.org/jira/browse/AVRO-3894 > https://github.com/apache/avro/pul

Re: [rust crate apache_avro] Alias and Serde Serialization

https://issues.apache.org/jira/browse/AVRO-3894 https://github.com/apache/avro/pull/2566 On Mon, Oct 23, 2023 at 8:54 PM Martin Grigorov wrote: > Hi, > > Please provide a complete test case that reproduces the problem and either > open a Pull Request or paste it here. > T

Re: [rust crate apache_avro] Alias and Serde Serialization

Hi, Please provide a complete test case that reproduces the problem and either open a Pull Request or paste it here. Then we’ll debug it and provide a fix. Regards, Martin On Mon, 23 Oct 2023 at 20:03, Josua Stingelin wrote: > Hei Guys, > > -- off topic > I hope this is the correct mailing

Re: Add support for nanosecond datetime types

sure technically it is well thought out! I just don't like seeing empty ticket/PR descriptions! If you don't have time (or don't see a reason) to write them then I see no reason to waste my time! Regards, Martin > > Kind regards, > Fokko > > > > > Op di 17 okt 2023 om 12:2

Re: [VOTE] New Avro logo (final)

On Mon, Oct 16, 2023 at 7:33 PM Oscar Westra van Holthe - Kind < os...@westravanholthe.nl> wrote: > Hi all, > > The results are in: with 6 binding votes (all cast within 6 hours), and no > non-binding votes, it's a near-tie between V9.2 and V3.1. > > These are the votes: > >- V9.2: 3 votes >

Re: Add support for nanosecond datetime types

Hi Fokko, Whenever I see an empty ticket and/or Github description (like https://issues.apache.org/jira/browse/AVRO-3884, https://github.com/apache/avro/pull/2554) the first thing that comes to my mind is to close it without giving an explanation too! If the reporter does not bother to help

Re: Rename default branch to be 'main'

Side effects: https://github.com/apache/avro/pull/1067#event-10568973359 and https://github.com/apache/avro/pull/660#event-10568973233 have been closed On Fri, Oct 6, 2023 at 9:18 AM Martin Grigorov wrote: > > > On Fri, Oct 6, 2023 at 4:02 AM Ismaël Mejía wrote: > >> Hello

Re: Rename default branch to be 'main'

On Fri, Oct 6, 2023 at 4:02 AM Ismaël Mejía wrote: > Hello, > > The change is done and all the CI jobs (save the ARM64 one are green, not > sure if the error is related). > You can switch your local branch from master to main and track the origin > by following these steps. > > git branch -m

Re: [VOTE] New Avro logo

V9.2 On Mon, Oct 2, 2023 at 3:14 PM Oscar Westra van Holthe - Kind < os...@westravanholthe.nl> wrote: > Hello everyone, > > The past month, there has been new progress on our search for a new logo ( > AVRO-3554 ). Thanks to > Emma Kellam and the

Re: [ANNOUNCE] New PMC member: Michael A. Smith

Congratulations, Michael! On Wed, Sep 20, 2023 at 9:00 PM Ryan Skraba wrote: > The Project Management Committee (PMC) for Apache Avro has invited > Michael A. Smith to the PMC and we are pleased to announce that he has > accepted. A PMC member helps manage and guide the direction of the >

Re: [ANNOUNCE] New committer: Oscar Westra van Holthe - Kind

Welcome to the team, Oscar! On Wed, Sep 20, 2023 at 9:00 PM Ryan Skraba wrote: > The Project Management Committee (PMC) for Apache Avro has invited > Oscar Westra van Holthe - Kind to become a committer and we are > pleased to announce that he has accepted. > > Oscar has done some really solid

Re: [ANNOUNCE] New committer: Christophe Le Saec

Welcome to the team, Christophe! On Wed, Sep 20, 2023 at 9:00 PM Ryan Skraba wrote: > The Project Management Committee (PMC) for Apache Avro has invited > Christophe Le Saec to become a committer and we are pleased to > announce that he has accepted. > > Christophe definitely puts in the work

Re: New Big Decimal Logical type

HI, On Mon, Sep 18, 2023 at 11:21 AM Christophe Le Saëc wrote: > Hello, > > This JIRA ticket would > introduce a new Big-Decimal logical type where precision and scale are not > given in the type definition, all is embedded in the value (this

Re: [VOTE] Release Apache Avro 1.11.3 RC1

+1 (binding) Tested the Rust SDK. Martin On Sun, Sep 17, 2023 at 11:40 AM Ryan Skraba wrote: > Hi everyone, > > I'd like to propose the following RC1 to be released as the official Apache > Avro 1.11.3 release. > > The commit id is 35ff8b997738e4d983871902d47bfb67b3250734 > * This corresponds

Re: [DISCUSS] Changing the Avro logo (revisited)

Hi, My favorite is v11.2 Blob Flat Icon - Rotated to Upward Angle with Blobs Adjusted Martin On Mon, Sep 18, 2023 at 10:06 AM Oscar Westra van Holthe - Kind < os...@westravanholthe.nl> wrote: > Hello everyone, > > TL;DR: have a look at the new logo designs at >

Re: [DISCUSS] Release Avro 1.11.3

On Fri, Sep 15, 2023 at 7:43 PM Ryan Skraba wrote: > And one month later... It looks like we're in a state OK to release > 1.11.3! There are no JIRA open on this FixVersion and I can build the > artifacts cleanly. I'm going to give this a start and try to get the > release candidates out this

Re: Generated code breaking change

On Thu, Aug 10, 2023 at 6:17 PM Oscar Westra van Holthe - Kind < os...@westravanholthe.nl> wrote: > On Thu, 10 Aug 2023 at 15:30, Christophe Le Saëc > wrote: > > > The PR fix the issue but *comes with breaking change* in case of name > > collision ('f' and 'F' are now transforms in getF() and

Re: Specification of namespaces

Hi, On Wed, Aug 9, 2023 at 6:30 PM Kousuke Saruta wrote: > Hi developers, > > I'd like to discuss the specification of namespace. > According to the specification, each dot separated portion of a namespace > should be [a-zA-Z_]][a-zA-Z0-9_]*. >

Re: [DISCUSS] Release maintenance and lifecycle

> > > > > > [1]: https://issues.apache.org/jira/browse/AVRO-2687 "Semantic > > versioning" > > > [2]: https://lists.apache.org/thread/6ppm20v5602w9nqz0nk5qz7mxnnt2tsw > > > "[DISCUSS] version numbers and where changes should land" > &

Re: [DISCUSS] Release maintenance and lifecycle

t; > "[DISCUSS] version numbers and where changes should land" > > [3]: https://lists.apache.org/thread/2rfnszd4dk36jxynpj382b1717gbyv1y > > "Release language modules separately" > > [4]: https://lists.apache.org/thread/rybf7vb514mtkr7swfld7b06g1kb2r3t > > &qu

Re: Implementing Python API Docs

On Fri, Jul 21, 2023 at 10:47 PM Martin Grigorov wrote: > > > On Fri, Jul 21, 2023 at 10:18 PM Michael A. Smith > wrote: > >> I did the cherry-pick, but I'm not sure I know how to test if it >> works. https://github.com/apache/avro/pull/2380 > > >

Re: Implementing Python API Docs

; of this learning curve, but I think it should be doable! > > > > All my best, Ryan > > > > > > On Fri, Jul 21, 2023 at 9:35 AM Martin Grigorov > wrote: > > > > > > On Thu, Jul 20, 2023 at 7:20 PM Michael A. Smith > > > > wr

Re: Implementing Python API Docs

On Thu, Jul 20, 2023 at 7:20 PM Michael A. Smith wrote: > OK, I've merged that PR and have made suggested changes to #2187. > Please let me know how I can help. > Thanks ! Hopefully this PR will be merged soon! > > On Thu, Jul 20, 2023 at 11:27 AM Martin Grigorov > wrote:

Re: Implementing Python API Docs

; > Does that seem reasonable? Yep! > > On Thu, Jul 20, 2023 at 2:30 AM Martin Grigorov > wrote: > > > > Hi Michael, > > > > The new website uses Hugo to build the static files. > > If you prefer to use Sphinx for the Python docs then I suggest to fo

Re: Implementing Python API Docs

Hi Michael, The new website uses Hugo to build the static files. If you prefer to use Sphinx for the Python docs then I suggest to follow the way of C/C++/C#/Java SDKs contribute their part of the docs in this PR -

Re: [DISCUSS] Release maintenance and lifecycle

I like Christophe's proposal ! On Tue, Jul 18, 2023 at 11:52 AM Christophe Le Saëc wrote: > Hello > I find this proposal relevant. > > to clarify : > > > From 1.12.0 on, I'd like to propose maintaining *two* major versions > > (i.e. 1.12.x and 1.11.x). That would allow us to deprecate and

Re: [DISCUSS] Release Avro 1.11.3

+1 from me ! On Wed, Jul 12, 2023 at 2:34 PM Ryan Skraba wrote: > The regression from AVRO-3789 looks like it a sufficient regression to > merit releasing 1.11.3, which should also cover some of the minor > bumps necessary for the Rust SDK. > > Any objection to doing another while the

Re: [VOTE] Release Apache Avro 1.11.2 RC1

. So, as a regression, IMHO it should be merged before 1.11.2 > > release ? > > > > Le mer. 5 juil. 2023 à 14:55, Martin Grigorov a > > écrit : > > > > > Hi, > > > > > > Sorry for the late reply! I was on vacation without access to > cmdline/IDE. &g

Re: [VOTE] Release Apache Avro 1.11.2 RC1

Hi, Sorry for the late reply! I was on vacation without access to cmdline/IDE. On Mon, Jul 3, 2023 at 6:09 PM Ryan Skraba wrote: > Oh, I forgot to address Martin's comments here -- I was waiting to see > if there were any other "minor" issues that might accumulate and > justify a new RC with

Re: [VOTE] Release Apache Avro 1.11.2 RC1

+1 to release 1.11.2 ! I've noticed a failing test in the Rust SDK - https://github.com/apache/avro/blob/master/lang/rust/avro/tests/shared.rs It fails when testing the apache_avro.tar.gz from https://dist.apache.org/repos/dist/dev/avro/avro-1.11.2-rc1/rust/ because it tries to run the "shared"

Re: computing the size of an avro encoded message

Hi Andrew, On Thu, May 18, 2023 at 12:12 PM Andrew Marlow wrote: > Hello everyone, > > I have just run into the problem discussed on SO at > > https://stackoverflow.com/questions/43738118/size-of-encoded-avro-message-without-encoding-it > > I am using avro from C++ and currently have a payload

Re: Python Issue with Optional UUIDs

Hi Daniel, Would you like to send a Pull Request with the fix and a test case ? Thank you! Martin On Wed, Apr 26, 2023 at 8:13 AM Daniel Young wrote: > Hi, > I believe there is an issue with the python library supporting a schema > with optional UUIDs. > The field should look like: > >

Re: Issues with website

a JIRA account for > you (see https://selfserve.apache.org/jira-account.html) or you can > create PRs on the documentation pages directly in the wiki. > > Thanks Martin for the pointers to where the pages exist in the repo > (at time of writing...) > > All my best, Ryan > > On T

Re: [Rust] derive AvroSchema for enums with named fields

Hi Mark, There is an issue about this - https://issues.apache.org/jira/browse/AVRO-3646 And a Pull Request - https://github.com/apache/avro/pull/1921 . It needs more work! Any feedback is welcome! On Thu, Apr 6, 2023 at 7:50 PM Mark de Jong wrote: > Hi, > > It would be great if you could

Re: Issues with website

Hi, On Tue, Apr 4, 2023 at 2:49 PM William Taylor wrote: > Dear Avro Developers, > > While doing some research as part of my employment, I noticed a couple of > issues about your website. I'm not sure if the dev mailing list is the > right place for issues with the website, but if not, I would

Re: [DISCUSS] Release Avro 1.11.2

a bad idea, needs anything specific for > > 1.11.2 or wants to help review / resolve some of these PRs marked for > > 1.11.2, I'd love to hear about it. > > > > In any case, I'm definitely going to propose a release shadowing > > session (maybe recorded?) that I di

Re: AVRO-1891 although marked as fixed at 1.9.1 it is still reproducible in 1.11.1

On Mon, Feb 27, 2023 at 3:24 PM vassilis spiliopoulos <2bi...@gmail.com> wrote: > Hi, > > I think AVRO-1891 (https://issues.apache.org/jira/browse/AVRO-1891) should > be reopened, as it affects too many people (including myself) and it is > quite mandatory functionality. Happy to provide more

Re: Parquet to Avro with Rust

Hi, On Sun, Feb 26, 2023 at 9:03 PM David Lacalle Castillo < dvdlacallecasti...@gmail.com> wrote: > Good afternoon, > > I have some parquet data that was created using Avro Parquet Writer of > Java. This parquet includes the Avro Schema inside the key > parquet.avro.schema of the metadata, I

Re: Release language modules separately

nt a specific test at any time no matter what is the SDK's version. > Le jeu. 12 janv. 2023 à 15:19, Martin Grigorov a > écrit : > > > On Thu, Jan 12, 2023 at 3:12 PM Christophe Le Saëc > > wrote: > > > > > With one github repo; how to manage share &g

Re: Release language modules separately

't see the problem. The main branch in the monorepo will consists of SDKs with various versions, but each SDK will have just one version at any time. Older versions will be in the release tags. > > > Le jeu. 12 janv. 2023 à 12:24, Martin Grigorov a > écrit : > > > On Wed, Jan 11,

Re: Release language modules separately

On Wed, Jan 11, 2023 at 9:27 PM Ryan Skraba wrote: > Hey -- how does this sound for rolling out this strategy. > > 1) No changes to 1.11 branch. We can release 1.11.2 to bring some of > the immediate bug and security fixes. > > 2) The next major release of Avro will be 12.0.0 for the

Re: Release language modules separately

MC member) will execute just the script(s) for the released SDK(s). Currently the release scripts use share/VERSION.txt as a shared resource. This will have to be re-thinked. > > Le mer. 4 janv. 2023 à 20:58, Martin Grigorov a > écrit : > > > Thanks, Ryan! > > > > I have fo

Re: Release language modules separately

r those ? > > Thanks for bringing this up and HAPPY NEW YEAR everybody! > > Ryan > > [1]: https://lists.apache.org/thread/rybf7vb514mtkr7swfld7b06g1kb2r3t > "[DISCUSS] Releases, versioning and lifecycle" > > > On Wed, Jan 4, 2023 at 1:05 PM Oscar Westra van Holthe - Kind &

Re: Deploy documentation via .asf.yaml

ocumentation My idea is to move the non-versioned content to https://github.com/apache/avro-site (a new Git repo) and leave only the versioned content in apache/avro#doc folder. Any objections ? Or better ideas ? On Fri, Dec 9, 2022 at 4:29 PM Martin Grigorov wrote: > I created https://issues.apa

Re: Release language modules separately

rability without > consulting a lookup table. > > Kind regards, > Oscar > > -- > Oscar Westra van Holthe - Kind > > Op di 3 jan. 2023 15:01 schreef Martin Grigorov : > > > Happy new year Avro community! > > I wish you to have a lot of fun while developin

Re: Release language modules separately

t; is the minor one. A patch release would be something like 1.11.1.1. > > Best Regards, > Khrystyna > > On Wed, Jan 4, 2023 at 1:02 AM Martin Grigorov > wrote: > > > Happy new year Avro community! > > I wish you to have a lot of fun while developing your pr

Release language modules separately

Happy new year Avro community! I wish you to have a lot of fun while developing your projects! I'd like to propose to make it possible to release a single module/lang. At the moment all modules share the same version and are being released together. The problem is that the release cadence is

Re: Improve compatibility check results for python client

Hi Oleksii, Would you like to send a Pull Request with the suggeted improvement ? Thank you in advance! Martin On Wed, Dec 21, 2022 at 11:27 AM Oleksii Shevtsov < alex.shevtsov1...@gmail.com> wrote: > Good morning, > > It seems like this email is the simplest way to signal about issues in >

Re: multiple fixes/changes for just one JIRA

Hi Andrew! Please send the PR! The C++ module is not actively developed at the moment and I'm afraid no one from the Avro committers will take a look at it any time soon. Hopefully other users will review and approve your PR and then me or someone else who is not familiar with the C++ code will

Re: How to get a JIRA account prior to creating a PR

Hi Andrew, Either here or priv...@avro.apache.org is fine! We didn't receive anything from you at private@ yet! Please send: userid, display name and email address. Martin On Sat, Dec 17, 2022 at 5:22 PM Andrew Marlow wrote: > Hello everyone, > > I have a fork of avro for a change I want to

Re: Update .NET ReflectReader and ReflectWriter related classes to be able override default behavior

Hello, On Wed, Dec 14, 2022 at 3:03 AM Khrystyna Popadyuk < khrystyna.popad...@gmail.com> wrote: > Hi people, > > For .NET two sets of reader/writer are available: Specific and Reflect. > My company has chosen reflect one as it has a list of benefits that are > important for us. However,

Re: Avro Schemas with external Dependancies - AVRO-3683

Hi Mark, On Mon, Dec 12, 2022 at 7:18 PM Mark Farnan wrote: > Hi All, > > A week or so back, I created. > https://issues.apache.org/jira/browse/AVRO-3683 (AVRO RUST) > Yes, sorry! I have a deadline at work and I don't have much time for bigger OSS tasks like this one right now. > I've been

Re: Deploy documentation via .asf.yaml

ts for builds before 1.11.1, and only > auto-deploy hugo builds. > > I think the new website is a great start, having a better build and > deploy would definitely help us make it better! I'm interested in > learning too ;) > > All my best, Ryan > > [1]: https://issues.apa

Deploy documentation via .asf.yaml

Hello, I'd like to propose changing the way the site/documentation is deployed at https://avro.apache.org. Currently it comes from Subversion: http://svn-master.apache.org/repos/asf/avro/site/publish I suggest to make use of .asf.yaml (

Re: Possible bug with avro-js with binary serdes and schema resolution

Hi Matthew, Since you are not subscribed to the mailing list your messages have to be moderated. I didn't notice anything from you at user@avro.a.o About JIRA - you can ask for an account here (dev@avro.a.o) or private@avro.a.o. We need an username, display name and email address to create one

Re: IDL schema parsing for the 21st century

Hi Oscar, Do those PRs really need to touch so many files ? All three PRs are huge (PR 1 - 102 changed files, 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

Re: IDL schema parsing for the 21st century

ead on bringing the > IDL syntax into the 21st century: > https://www.mail-archive.com/dev@avro.apache.org/msg29216.html > > A few months later, I had the first PR ready, which received some feedback. > Thank you Ryan Skraba, Martin Grigorov and Christophe Le Saëc! > > This is now

Re: Programming languages for Avro

Hello, I don't see a need to remove any SDK for now. As with any other open source project the development is driven by users' needs. IMO it is not necessary a feature to be added to all SDKs at the same time, i.e. the SDKs don't need to evolve in the same pace. Whenever a user needs some

Re: [DISCUSS] Release Avro 1.11.2

+1 for 1.11.2 IMO Jackson could be upgraded to 2.13.x only for 1.12.0. 2.12.7 is not affected by the CVEs On Fri, Nov 4, 2022, 20:07 Ryan Skraba wrote: > It looks like there's been a couple of CVE fixes in dependencies that > we might want to have! See AVRO-3656, and perhaps AVRO-3658 (not

Re: manylinux piwheel not found

Hi, I think your problem is that https://pypi.org/project/avro/#files does not provide any wheels, so " --only-binary=:all:" cannot be used. On Thu, Oct 27, 2022 at 8:13 AM Matt Fysh wrote: > I'm developing a python application on Mac, and deploying to a linux > environment, so when building

Re: Proposed enhancement: configure mapping of AVRO namespace to Java packagename

Hi Simon, On Wed, Oct 12, 2022, 18:17 wrote: > Hi All, > > My employer is (very happily) using avro-maven-plugin in many projects. > However we would like to be able to control the packagenames for Java > classes generated from AVRO schemas (ie not just have > packagename=schemanamespace). I

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

+1 (binding) Any idea how this Gradle-based project will be become a sub-module of Avro (a Maven-based project) ? Maybe with exec-maven-plugin ?! I haven't seen such setups so far. Martin On Mon, Oct 10, 2022 at 7:59 PM Ryan Skraba wrote: > Hello everyone! > > The developer(s) of

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

Hi Cody, I think these extra checks for equality will affect the performance for all users. Woud it be possible to wrap the "put" calls with "if !containsKey(name)" check in your code ? On Thu, Oct 6, 2022 at 2:23 PM Cody Jones wrote: > Hey, > > We are using Avro via the Clojure wrapper

Re: Probable bug in Python schema parser (tested on v1.11.0)

Hi James, You can create an issue at https://issues.apache.org/jira/projects/AVRO. Please try with Avro 1.11.1 before that! Regards, Martin On Fri, Sep 23, 2022 at 2:50 AM James Sarrett wrote: > Hi there, > > I was going to submit a ticket on Jira, but I couldn't figure out how. I'm >

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

Re: Avro Java Version

Hi, I am a big supporter of the progress (I test OpenJDK early access releases with few Apache projects and keep those JDKs up-to-date in ASF Jenkins and Buildbot environments)! But before raising the Java version maybe we should think what it would bring to Avro ? Which Java 11 features would

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

> > On Sep 1, 2022, at 16:34, Martin Grigorov wrote: > > > >  > > > > > >> On Thu, Sep 1, 2022 at 11:08 PM Brennan Vincent > wrote: > >> > >> > >> On 2022-08-31 17:18, Martin Grigorov wrote: > >>

Re: [DISCUSS] Pull request template changes

Hi, +1 for the improvements! I hope that less people will ignore it now after explicitly stating that if the template is ignored then the review will be postponed :-) Martin On Thu, Sep 1, 2022 at 10:04 PM Ryan Skraba wrote: > Hey everybody -- > > For the most part, it seems that the PR

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

On Thu, Sep 1, 2022 at 11:08 PM Brennan Vincent wrote: > > > On 2022-08-31 17:18, Martin Grigorov wrote: > > On Wed, Aug 31, 2022 at 9:59 PM Brennan Vincent > > wrote: > > > >> > >> > >> On 2022-08-31 13:38, Ryan Skraba wrote: > >&g

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

t;>>>> gives schema authors more options. > >>>>> > >>>>> But if you're using namespaces at all, there must be a reason for > it. As a > >>>>> schema author, you've made the decision to group your schemata. > >>>>> &g

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

gt;> I.e., explicitly disallow identifiers to start with a dot (and > disallow > > >>> references to the null namespace from within another namespace). > > >>> > > >>> > > >>> Kind regards, > > >>> Oscar >

  1   2   >