[jira] [Created] (AVRO-3861) [Build] Add RAT exclusions for python docs

[Ryan Skraba (Jira)]

Ryan Skraba created AVRO-3861:
-

 Summary: [Build] Add RAT exclusions for python docs
 Key: AVRO-3861
 URL: https://issues.apache.org/jira/browse/AVRO-3861
 Project: Apache Avro
  Issue Type: Bug
  Components: build
Affects Versions: 1.12.0, 1.11.3
Reporter: Ryan Skraba


When following the release process and doing a *./build.sh clean test dist* we 
get the following error:

{code}
[INFO] --- apache-rat-plugin:0.15:check (default) @ avro-toplevel ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from /home/ryan.skraba/avro/.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 88 implicit excludes.
[INFO] 131 explicit excludes.
[INFO] 5630 resources included
[INFO] Rat check: Summary over all files. Unapproved: 17, unknown: 17, 
generated: 0, approved: 1580 licenses.
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from /home/ryan.skraba/avro/.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 88 implicit excludes.
[INFO] 131 explicit excludes.
[INFO] 5630 resources included
[WARNING] Files with unapproved licenses:
  lang/py/docs/build/html/searchindex.js
  lang/py/docs/build/html/.buildinfo
  lang/py/docs/build/html/search.html
  lang/py/docs/build/html/py-modindex.html
  lang/py/docs/build/html/genindex.html
  lang/py/docs/build/html/intro.html
  lang/py/docs/build/html/index.html
  lang/py/docs/build/html/automodule.html
  lang/py/docs/build/html/_static/alabaster.css
  lang/py/docs/build/html/_static/custom.css
  lang/py/docs/build/html/_static/basic.css
  lang/py/docs/build/html/_static/doctools.js
  lang/py/docs/build/html/_static/documentation_options.js
  lang/py/docs/build/html/_static/language_data.js
  lang/py/docs/build/html/_static/searchtools.js
  lang/py/docs/build/html/_static/sphinx_highlight.js
  lang/py/docs/build/html/_static/pygments.css
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  4.428 s
[INFO] Finished at: 2023-09-20T12:50:06Z
[INFO] 
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.15:check 
(default) on project avro-toplevel: Too many files with unapproved license: 17 
See RAT report in: /home/ryan.skraba/avro/target/rat.txt -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
{code}

The workaround is to do a `./build.sh clean test` followed by a `./build.sh 
clean dist`, but this should probably be fixed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] iemejia opened a new pull request, #2504: AVRO-3411: Fix devcontainers build

[via GitHub]

iemejia opened a new pull request, #2504:
URL: https://github.com/apache/avro/pull/2504

   Avro's devcontainers build fails, it misses the context section because of 
the relative path to the Dockerfile. Also the extensions section showed a 
warning. All should be good now.
   
   R: @martin-g 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [avro] clesaec merged pull request #2392: AVRO-2511: add case for sync

[via GitHub]

clesaec merged PR #2392:
URL: https://github.com/apache/avro/pull/2392


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: New Big Decimal Logical type

[Martin Grigorov]

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 new
> logical type does not replace current one). This is useful when you need
> bigdecimal without knowing anything about the values when defining the avro
> type.
>
> For the moment, there is only one PR for Java and one for Rust.
> So, can we introduce this new feature knowing there is no implementation
> for other module (at least for the moment) ?
>

I am OK with this approach !
Do you think it would be a good idea to mark this new logical type as
experimental in the specification ?



>
> Regards,
> Christophe.
>

[jira] [Created] (AVRO-3862) Add aliases and doc methods to Schema in Rust SDK

[Kousuke Saruta (Jira)]

Kousuke Saruta created AVRO-3862:


 Summary: Add aliases and doc methods to Schema in Rust SDK
 Key: AVRO-3862
 URL: https://issues.apache.org/jira/browse/AVRO-3862
 Project: Apache Avro
  Issue Type: Improvement
  Components: rust
Affects Versions: 1.12.0
Reporter: Kousuke Saruta


Named types (Record, Enum and Fixed) have common attributes {*}name{*}, 
*aliases* and {*}doc{*}.
We have already have *fn name* in Schema so it's nice to have *fn aliases* and 
*fn doc* too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] sarutak opened a new pull request, #2505: AVRO-3862: [Rust] Add aliases and doc methods to Schema in Rust SDK

[via GitHub]

sarutak opened a new pull request, #2505:
URL: https://github.com/apache/avro/pull/2505

   AVRO-3862
   
   ## What is the purpose of the change
   This PR proposes to add `fn aliases` and `fn doc` to `Schema`.
   
   Named types (Record, Enum and Fixed) have common attributes `name`, 
`aliases` and `doc`.
   We have already have `fn name` in Schema so it's nice to have `fn aliases` 
and `fn doc` too.
   
   ## Verifying this change
   Add new tests.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (no)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [avro] iemejia merged pull request #2504: AVRO-3411: Fix devcontainers build

[via GitHub]

iemejia merged PR #2504:
URL: https://github.com/apache/avro/pull/2504


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: New Big Decimal Logical type

[Oscar Westra van Holthe - Kind]

On Wed, 20 Sept 2023 at 15:53, Martin Grigorov  wrote:

> On Mon, Sep 18, 2023 at 11:21 AM Christophe Le Saëc 
> wrote:
> > This JIRA ticket  would
> > introduce a new Big-Decimal logical type [...]
> >
> > For the moment, there is only one PR for Java and one for Rust.
> > So, can we introduce this new feature knowing there is no implementation
> > for other module (at least for the moment) ?
>
> I am OK with this approach !
> Do you think it would be a good idea to mark this new logical type as
> experimental in the specification ?
>

Yes, I do.

There are similarities with the "duration" logical type: that is available
as logical type in most (all?) implementations, but using actual values of
that type is (AFAIK) only possible in Rust. The Java codebase, for example,
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 

[jira] [Created] (AVRO-3863) Delete temporary test data after tests finish

[Kousuke Saruta (Jira)]

Kousuke Saruta created AVRO-3863:


 Summary: Delete temporary test data after tests finish
 Key: AVRO-3863
 URL: https://issues.apache.org/jira/browse/AVRO-3863
 Project: Apache Avro
  Issue Type: Improvement
  Components: java
Affects Versions: 1.12.0
Reporter: Kousuke Saruta


Tests for Java SDK creates some test data, which are left even after tests 
finish.
{code}
ls -1 /tmp/*.avro
/tmp/junit1533190586260098046testMappedByteBuffer.avro
/tmp/junit3099644739767498712testMappedByteBuffer.avro
/tmp/junit4466003251314064556testMappedByteBuffer.avro
/tmp/junit4974226498248565286testMappedByteBuffer.avro
/tmp/junit6473921034404349045testMappedByteBuffer.avro
/tmp/junit8662732084083941415testMappedByteBuffer.avro
/tmp/random.avro
/tmp/testIgnoreSchemaValidationOnRead275054571669736256.avro
/tmp/testIgnoreSchemaValidationOnRead4615547521362396523.avro
/tmp/testIgnoreSchemaValidationOnRead4955268403025511495.avro
/tmp/testIgnoreSchemaValidationOnRead5426593551205571746.avro
/tmp/testIgnoreSchemaValidationOnRead7554021276748093417.avro
/tmp/testIgnoreSchemaValidationOnRead8241302423385070851.avro
/tmp/testInputStreamEOF3549506421974960237.avro
/tmp/testInputStreamEOF4423343183305481378.avro
/tmp/testInputStreamEOF7397178073669402143.avro
/tmp/testInputStreamEOF8065492409408481522.avro
/tmp/testInputStreamEOF8087280538995909098.avro
/tmp/testInputStreamEOF8719004614093216771.avro
/tmp/testInvalidMagicBytes1940432228654910095.avro
/tmp/testInvalidMagicBytes2703760186774533143.avro
/tmp/testInvalidMagicBytes5088097518917799234.avro
/tmp/testInvalidMagicBytes863787801374013591.avro
/tmp/testInvalidMagicBytes887543761182735490.avro
/tmp/testInvalidMagicBytes980334707534164945.avro
/tmp/testInvalidMagicLength1346115615984572207.avro
/tmp/testInvalidMagicLength1511998921770126285.avro
/tmp/testInvalidMagicLength1824057536245960603.avro
/tmp/testInvalidMagicLength2005669502062311523.avro
/tmp/testInvalidMagicLength7068591900276715585.avro
/tmp/testInvalidMagicLength8356756206873381473.avro
/tmp/testThrottledInputStream2962195154373996754.avro
/tmp/testThrottledInputStream3610702487927451328.avro
/tmp/testThrottledInputStream4661398720877824185.avro
/tmp/testThrottledInputStream5592809458916764863.avro
/tmp/testThrottledInputStream648963793454476.avro
/tmp/testThrottledInputStream8013323018361761899.avro
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (AVRO-3864) [Build] Do a better clean based on the .gitignore file

[Ryan Skraba (Jira)]

Ryan Skraba created AVRO-3864:
-

 Summary: [Build] Do a better clean based on the .gitignore file
 Key: AVRO-3864
 URL: https://issues.apache.org/jira/browse/AVRO-3864
 Project: Apache Avro
  Issue Type: Bug
Reporter: Ryan Skraba


>From https://github.com/apache/avro/pull/2500 (Thanks [~zoltan_csizmadia]!) 

If all of the target binaries and built files are included in the .gitignore 
file, then *git clean -dXf* will remove them (note the capital X).  This could 
be a better way to make sure the build directory doesn't have any left over 
residue from previous dev work.

The only downside to using git as "The Source of Clean" is that **./build.sh 
clean** when building from the source tar.gz (without git) wouldn't work.  That 
doesn't really bother me too much, as long as **./build.sh dist** works from 
the source tar.

Maybe this might be best applied in **./build.sh veryclean** or just remove the 
*clean* target to this script entirely and document this better way?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] sarutak opened a new pull request, #2506: AVRO-3863: [Java] Delete temporary test data after tests finish

[via GitHub]

sarutak opened a new pull request, #2506:
URL: https://github.com/apache/avro/pull/2506

   AVRO-3863
   
   ## What is the purpose of the change
   This PR proposes to delete temporary test data generated by tests for Java 
SDK.
   Tests for Java SDK creates some test data, which are left even after tests 
finish.
   ```
   ls -1 /tmp/*.avro
   /tmp/junit1533190586260098046testMappedByteBuffer.avro
   /tmp/junit3099644739767498712testMappedByteBuffer.avro
   /tmp/junit4466003251314064556testMappedByteBuffer.avro
   /tmp/junit4974226498248565286testMappedByteBuffer.avro
   /tmp/junit6473921034404349045testMappedByteBuffer.avro
   /tmp/junit8662732084083941415testMappedByteBuffer.avro
   /tmp/random.avro
   /tmp/testIgnoreSchemaValidationOnRead275054571669736256.avro
   /tmp/testIgnoreSchemaValidationOnRead4615547521362396523.avro
   /tmp/testIgnoreSchemaValidationOnRead4955268403025511495.avro
   /tmp/testIgnoreSchemaValidationOnRead5426593551205571746.avro
   /tmp/testIgnoreSchemaValidationOnRead7554021276748093417.avro
   /tmp/testIgnoreSchemaValidationOnRead8241302423385070851.avro
   /tmp/testInputStreamEOF3549506421974960237.avro
   /tmp/testInputStreamEOF4423343183305481378.avro
   /tmp/testInputStreamEOF7397178073669402143.avro
   /tmp/testInputStreamEOF8065492409408481522.avro
   /tmp/testInputStreamEOF8087280538995909098.avro
   /tmp/testInputStreamEOF8719004614093216771.avro
   /tmp/testInvalidMagicBytes1940432228654910095.avro
   /tmp/testInvalidMagicBytes2703760186774533143.avro
   /tmp/testInvalidMagicBytes5088097518917799234.avro
   /tmp/testInvalidMagicBytes863787801374013591.avro
   /tmp/testInvalidMagicBytes887543761182735490.avro
   /tmp/testInvalidMagicBytes980334707534164945.avro
   /tmp/testInvalidMagicLength1346115615984572207.avro
   /tmp/testInvalidMagicLength1511998921770126285.avro
   /tmp/testInvalidMagicLength1824057536245960603.avro
   /tmp/testInvalidMagicLength2005669502062311523.avro
   /tmp/testInvalidMagicLength7068591900276715585.avro
   /tmp/testInvalidMagicLength8356756206873381473.avro
   /tmp/testThrottledInputStream2962195154373996754.avro
   /tmp/testThrottledInputStream3610702487927451328.avro
   /tmp/testThrottledInputStream4661398720877824185.avro
   /tmp/testThrottledInputStream5592809458916764863.avro
   /tmp/testThrottledInputStream648963793454476.avro
   /tmp/testThrottledInputStream8013323018361761899.avro
   ```
   
   ## Verifying this change
   The tests still pass even after this change.
   Also, test data are deleted.
   ```
   ls /tmp/*.avro
   ls: cannot access '/tmp/*.avro': No such file or directory
   ```
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (no)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: New Big Decimal Logical type

[Ryan Skraba]

Hello!  There's a couple things going on, but I think this new type
needs to be better specified in in the documentation before merging!

Specifically, how are the bytes constructed and why was this
representation chosen?  Is there a better, more neutral represention
where the underlying type could still be useful in languages that
don't support this logical type? I'd also be interested in finding a
less "Java" name for arbitrary precision values than BigDecimal if
possible!

Historically, the stringable represention of an BigDecimal was used
for these value.  I think we'd have to make an argument that the
binary representation is more compact and/or efficient than this.

In my experience, there aren't many use cases that require an
arbitrary precision per value (as opposed to decimal, which sets it
for the schema), and it's usually because "we don't know the precision
of our data yet".   As an example, Google Cloud Spanner recommends
using Strings when a predefined precision and scale is unsatisfactory
for a column[1].  Is there a better way for us to help the use when
they don't know the precision of data they expect to work with?

If there's other use cases for arbitrary sized data, maybe we can
align on a solution!

All my best, Ryan

[1]: 
https://cloud.google.com/spanner/docs/storing-numeric-data#recommendation_store_arbitrary_precision_numbers_as_strings

On Wed, Sep 20, 2023 at 6:19 PM Oscar Westra van Holthe - Kind
 wrote:
>
> On Wed, 20 Sept 2023 at 15:53, Martin Grigorov  wrote:
>
> > On Mon, Sep 18, 2023 at 11:21 AM Christophe Le Saëc 
> > wrote:
> > > This JIRA ticket  would
> > > introduce a new Big-Decimal logical type [...]
> > >
> > > For the moment, there is only one PR for Java and one for Rust.
> > > So, can we introduce this new feature knowing there is no implementation
> > > for other module (at least for the moment) ?
> >
> > I am OK with this approach !
> > Do you think it would be a good idea to mark this new logical type as
> > experimental in the specification ?
> >
>
> Yes, I do.
>
> There are similarities with the "duration" logical type: that is available
> as logical type in most (all?) implementations, but using actual values of
> that type is (AFAIK) only possible in Rust. The Java codebase, for example,
> 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 

[jira] [Created] (AVRO-3865) [Build][perl] Files are leftover after a build

[Ryan Skraba (Jira)]

Ryan Skraba created AVRO-3865:
-

 Summary: [Build][perl] Files are leftover after a build
 Key: AVRO-3865
 URL: https://issues.apache.org/jira/browse/AVRO-3865
 Project: Apache Avro
  Issue Type: Bug
Reporter: Ryan Skraba


After `./build.sh dist`, this file remains

{code}
On branch master
Your branch is up to date with 'apache/master'.

Untracked files:
  (use "git add ..." to include in what will be committed)
lang/perl/VERSION.txt
{code}

This probably should just be put in the .gitignore



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] RyanSkraba opened a new pull request, #2507: [docs] Announce new committers

[via GitHub]

RyanSkraba opened a new pull request, #2507:
URL: https://github.com/apache/avro/pull/2507

   ## What is the purpose of the change
   
   Welcome new committers and PMC to the community! 
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? no
   - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[ANNOUNCE] New PMC member: Michael A. Smith

[Ryan Skraba]

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
project.

Notably, Michael has taken a leadership role in ensuring the quality
of the Python SDK, lending his expertise to ensure that Avro has a
place in the python community, while keeping our implementation
up-to-date with standards and modern versions.  It's not an easy task,
and we appreciate all he does!

Thanks so much, Michael!  Ryan

[ANNOUNCE] New committer: Christophe Le Saec

[Ryan Skraba]

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 and, has an impressive breadth
of knowledge about the languages of the Avro SDK!

As an ASF project, we tend to be very conservative about making
changes, and Christophe brings in fresh ideas and very quickly
proposes concrete implementations to prove them.  He has a good
understanding of Avro, the motivation to move things forward, and the
expertise to make changes!  At the same time, he's easy to talk to and
flexible in coming to a consensus.

Thanks for all your hard work!

All my best, Ryan

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

[Ryan Skraba]

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 work on the IDL and JavaCC parts of
the Java SDK.  We trust his work and think it's of exceptionally high
quality.  From the start, he has already doing much of the work of a
committer, demonstrated by his continuous presence in commenting JIRA,
reviewing PRs as well as encouraging and insightful words on the
mailing list.

As a bonus, in his spare time, Oscar also maintains the IntelliJ
plugin for [IDL
support](https://plugins.jetbrains.com/plugin/15728-apache-avro-idl-schema-support)!

Thanks for all your hard work, and welcome!

All my best regards, Ryan

[jira] [Created] (AVRO-3866) [Build][Python] Files are leftover after a build

[Kousuke Saruta (Jira)]

Kousuke Saruta created AVRO-3866:


 Summary: [Build][Python] Files are leftover after a build
 Key: AVRO-3866
 URL: https://issues.apache.org/jira/browse/AVRO-3866
 Project: Apache Avro
  Issue Type: Bug
Reporter: Kousuke Saruta


Similar to AVRO-3865, lang/py/VERSION.txt is leftover after lang/py/build.sh doc



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] sarutak opened a new pull request, #2508: AVRO-3865, AVRO-3866: [Build][Perl][Python] Add VERSION.txt to .gitignore

[via GitHub]

sarutak opened a new pull request, #2508:
URL: https://github.com/apache/avro/pull/2508

   AVRO-3865
   AVRO-3855
   
   ## What is the purpose of the change
   This PR proposes to add `lang/perl/VERSION.txt` and `lang/py/VERSION.txt` to 
`.gitignore`.
   
   They are created when we run `lang/perl/build.sh doc` and `lang/py/build.sh 
doc`
   
   ## Verifying this change
   Confirmed `git status` doesn't mark `VERSION.txt` as untracked.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (no)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Release Apache Avro 1.11.3 RC1

[Ismaël Mejía]

+1 (binding)

I struggled a lot to do a full build with the docker image, we should
probably improve some things there. Apart of this all the rest looked
good, sigs/shas ok I mostly tested in detail the Java bits.

Ismaël

On Tue, Sep 19, 2023 at 5:37 PM Fokko Driesprong  wrote:
>
> Thanks for running this Ryan!
>
> +1 (binding) tested against Apache Iceberg.
>
> Cheers, Fokko
>
> Op di 19 sep 2023 om 14:45 schreef Kousuke Saruta :
>
> > +1 (non-binding)
> >
> > Kousuke
> >
> > 2023年9月17日(日) 17:40 Ryan Skraba :
> >
> > > 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 to the tag: release-1.11.3-rc1
> > > * https://github.com/apache/avro/releases/tag/release-1.11.3-rc1
> > >
> > > The release tarball, signature, and checksums are here (revision r64034)
> > > * https://dist.apache.org/repos/dist/dev/avro/avro-1.11.3-rc1/
> > >
> > > You can find the KEYS file here:
> > > * https://dist.apache.org/repos/dist/dev/avro/KEYS
> > >
> > > Binary artifacts for Java are staged in Nexus here:
> > > *
> > >
> > https://repository.apache.org/content/groups/staging/org/apache/avro/avro/1.11.3/
> > >
> > > This release includes ~40 Jira issues:
> > > *
> > >
> > https://issues.apache.org/jira/issues/?jql=project%3DAVRO%20AND%20fixVersion%3D1.11.3
> > >
> > > Please download, verify, and test. This vote will remain open for at
> > least
> > > 72 hours.  I would like to close at 11h59 UTC Thursday, September 21th,
> > > 2023.
> > >
> > > [ ] +1 Release this as Apache Avro 1.11.3
> > > [ ] +0
> > > [ ] -1 Do not release this because...
> > >
> > > Best regards,
> > > Ryan Skraba
> > > [Countdown to vote]:
> > > https://www.timeanddate.com/countdown/to?iso=20230921T1159&p0=1440
> > >
> >

[jira] [Created] (AVRO-3867) Link to the Python API doc is broken

[Kousuke Saruta (Jira)]

Kousuke Saruta created AVRO-3867:


 Summary: Link to the Python API doc is broken
 Key: AVRO-3867
 URL: https://issues.apache.org/jira/browse/AVRO-3867
 Project: Apache Avro
  Issue Type: Bug
Reporter: Kousuke Saruta


I built the website by ./build.sh dist and then tried to access to the Python 
API doc but the link seems broken.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] sarutak opened a new pull request, #2509: AVRO-3867: [Python][Build] Fix the broken link to the Python API doc in the web site

[via GitHub]

sarutak opened a new pull request, #2509:
URL: https://github.com/apache/avro/pull/2509

   AVRO-3867
   
   ## What is the purpose of the change
   This PR fixes an issue that the link to the Python API doc in the web site 
is broken.
   I built the website by `./build.sh` dist and then tried to access to the 
Python API doc but the link seems broken.
   
   The cause is `py/build.sh dist` doesn't generate the document.
   So this PR includes a fix to generate the document when we run `py/build.sh 
dist`.
   
   ## Verifying this change
   Built the web site and confirmed the link is available.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (no)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (AVRO-3868) Check consistency between the doc comment in lib.rs and README.md

[Kousuke Saruta (Jira)]

Kousuke Saruta created AVRO-3868:


 Summary: Check consistency between the doc comment in lib.rs and 
README.md
 Key: AVRO-3868
 URL: https://issues.apache.org/jira/browse/AVRO-3868
 Project: Apache Avro
  Issue Type: Improvement
  Components: build, rust
Affects Versions: 1.12.0
Reporter: Kousuke Saruta


AVRO-3849 added cargo-rdme.
So it's nice if we can check the consistency between avro/src/lib.rs and 
avro/README.md



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] sarutak opened a new pull request, #2510: AVRO-3868: [Rust][CI] Check consistency between the doc comment in lib.rs and README.md

[via GitHub]

sarutak opened a new pull request, #2510:
URL: https://github.com/apache/avro/pull/2510

   AVRO-3868
   
   ## What is the purpose of the change
   This PR proposes to add a consistency check between the doc comment in 
`avro/src/lib.rs` and `avro/README.md`.
   AVRO-3849 added cargo-rdme so it's nice if we can check the consistency 
between them.
   
   ## Verifying this change
   Done by GitHub Actions.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (no)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[jira] [Created] (AVRO-3869) Error parsing fixed logical schemas

[Paulo Humberto Lacerda e Silva (Jira)]

Paulo Humberto Lacerda e Silva created AVRO-3869:


 Summary: Error parsing fixed logical schemas
 Key: AVRO-3869
 URL: https://issues.apache.org/jira/browse/AVRO-3869
 Project: Apache Avro
  Issue Type: Bug
  Components: csharp
Affects Versions: 1.11.2
Reporter: Paulo Humberto Lacerda e Silva


Logical types works only for primitive types, and I can't deserialize an fixed 
type, like this one:

 
{code:java}
{
 "type": "fixed",
 "name": "LogicalFixed",
 "logicalType": "decimal",
 "precision": 4,
 "scale": 2,
  "size": 10
}

{code}
An exception is SchemaParseException raised ("Undefined name: fixed at 'type'")


This schema is autogenerated by PySpark, from a decimal type, and can't be 
parsed.
Spark docs: https://spark.apache.org/docs/latest/sql-data-sources-avro.html

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [avro] sarutak opened a new pull request, #2511: Minor: [Perl][Test] Suppress warning in interop-data-test for Perl SDK

[via GitHub]

sarutak opened a new pull request, #2511:
URL: https://github.com/apache/avro/pull/2511

   ## What is the purpose of the change
   This PR aims to suppress a warning in interop-data-test for Perl SDK.
   
   When we run `./build.sh test` or `lang/perl/build.sh interop-data-test`, we 
get the following message.
   ```
   Name "Avro::DataFile::ValidCodec" used only once: possible typo
   ``
   
   This warning message sometimes appears in the result of CI.
   https://github.com/apache/avro/actions/runs/6255050186
   
   ## Verifying this change
   Confirmed the warning message is disappeared by running `lang/perl/build.sh 
interop-data-test`.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? (no)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [avro] paulohumberto42 opened a new pull request, #2512: AVRO-3869 [chsarp] Fix logical fixed schema support

[via GitHub]

paulohumberto42 opened a new pull request, #2512:
URL: https://github.com/apache/avro/pull/2512

   
   
   ## What is the purpose of the change
   
   Logical types works only for primitive types, and I can't deserialize an 
fixed type, like this one:
   
   ```javascript
   {
"type": "fixed",
"name": "LogicalFixed",
"logicalType": "decimal",
"precision": 4,
"scale": 2,
 "size": 10
   }

   ``` 
   
   A SchemaParseException is raised ("Undefined name: fixed at 'type'")
   This schema is autogenerated by PySpark, from a decimal type, and can't be 
parsed.
   Spark docs: https://spark.apache.org/docs/latest/sql-data-sources-avro.html
   
   
   ## Verifying this change
   This change added tests and can be verified as follows:
   ```csharp
   [TestCase("{ \"type\": \"fixed\", \"name\": \"LogicalFixed\", 
\"logicalType\": \"decimal\", \"precision\": 4, \"scale\": 2, \"size\": 10 }", 
"decimal", 10)]
   public void TestLogicalFixed(string s, string logicalType, int size)
   {
   Schema sc = Schema.Parse(s);
   Assert.AreEqual(Schema.Type.Logical, sc.Tag);
   LogicalSchema logsc = sc as LogicalSchema;
   FixedSchema basesc = logsc.BaseSchema as FixedSchema;
   Assert.AreEqual(Schema.Type.Fixed, basesc.Tag);
   Assert.AreEqual(size, basesc.Size);
   Assert.AreEqual(logicalType, logsc.LogicalType.Name);
   
   testEquality(s, sc);
   testToString(sc);
   }
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [avro] martin-g merged pull request #2511: Minor: [Perl][Test] Suppress warning in interop-data-test for Perl SDK

[via GitHub]

martin-g merged PR #2511:
URL: https://github.com/apache/avro/pull/2511


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [avro] martin-g merged pull request #2507: [docs] Announce new committers

[via GitHub]

martin-g merged PR #2507:
URL: https://github.com/apache/avro/pull/2507


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@avro.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [ANNOUNCE] New committer: Christophe Le Saec

[Martin Grigorov]

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 and, has an impressive breadth
> of knowledge about the languages of the Avro SDK!
>
> As an ASF project, we tend to be very conservative about making
> changes, and Christophe brings in fresh ideas and very quickly
> proposes concrete implementations to prove them.  He has a good
> understanding of Avro, the motivation to move things forward, and the
> expertise to make changes!  At the same time, he's easy to talk to and
> flexible in coming to a consensus.
>
> Thanks for all your hard work!
>
> All my best, Ryan
>

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

[Martin Grigorov]

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 work on the IDL and JavaCC parts of
> the Java SDK.  We trust his work and think it's of exceptionally high
> quality.  From the start, he has already doing much of the work of a
> committer, demonstrated by his continuous presence in commenting JIRA,
> reviewing PRs as well as encouraging and insightful words on the
> mailing list.
>
> As a bonus, in his spare time, Oscar also maintains the IntelliJ
> plugin for [IDL
> support](
> https://plugins.jetbrains.com/plugin/15728-apache-avro-idl-schema-support
> )!
>
> Thanks for all your hard work, and welcome!
>
> All my best regards, Ryan
>

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

[Martin Grigorov]

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
> project.
>
> Notably, Michael has taken a leadership role in ensuring the quality
> of the Python SDK, lending his expertise to ensure that Avro has a
> place in the python community, while keeping our implementation
> up-to-date with standards and modern versions.  It's not an easy task,
> and we appreciate all he does!
>
> Thanks so much, Michael!  Ryan
>