Hi, I have some pull requests on a couple of issues related to the python
implementations of avro that I opened about 3 weeks ago. Since there has
been no response other than bots, I'm wondering if the maintainer of the
python parts of avro is still active.
If they are not still active or availabl
I've begun trying to add type hints to avro/lang/py3. This is uncovering a
lot of variance problems in the current implementation. I need some advice
and guidance.
For example, class Schema has a constructor like
def __init__(
self,
type: str,
other_props: typing.Optional[typi
Hi, just to assure you that there are other people on this list... hi. I
also have sent things to the list and heard only crickets.
That said, I know of no schema compatibility rules changed between 1.8.1
and .2. I do think this is the right list, but it is very quiet.
On Tue, Oct 9, 2018 at 12:2
Bringing this back up: I think avro and avro-python3 are mostly compatible,
so we really just need to invent a way to make people switch automatically.
We could almost have py3 install avro as a dependency. The thing is, both
packages are under the root namespace `avro`, so you can't trivially have
Hi, Cris,
I'm happy to take a look.
On Thu, Jul 23, 2020 at 20:23 Cris Ewing wrote:
> Greetings, avro devs.
>
> We've been using avro for a short while now and have run into an issue with
> validation. Our problem is that we have a number of schemas that are quite
> large. When working on get
Python 2 has been officially obsolete since January 1. I propose we drop
support for it.
If we decide to continue supporting it, note that pip, the (main) Python
package management tool, will itself only support python3 in its next
release. So installing avro with python 2 will have to be done mor
M Cris Ewing
> wrote:
>
> > +1
> >
> > (to be clear, I'm not certain my vote counts for anything other than
> > advisory)
> >
> > yours
> >
> > c
> >
> > On Tue, Jul 28, 2020 at 6:15 AM Michael A. Smith
> > wrote:
> &g
We've had mypy, the Python type checker, running in Travis-CI on
lang/py for a little while. However, mypy doesn't actually check code
unless it has type hints, so it has been doing very little. Now that
we are only supporting Python 3.5 and up, we can add real type hints!
I'm excited about this,
There was a thread on this list in May 2019 headed "Automate python
formatting" that touched on dependabot. At the time, Fokko, and you,
Ismaël, were discussing that dependabot might violate Apache rules about
modifying the code. Has that been worked out?
I'm otherwise totally in favor of this.
O
I propose that we track pip, the official Python package installer, in
its Python support policy. More formally, I propose that if pip
creates a changelog entry such as
https://pip.pypa.io/en/latest/news/#b1-2020-10-31, indicating a clear
intent to drop support for some version of Python, that we s
I created a PR to implement our tests in GitHub actions. I'd like to
know if other folks are interested in me pursuing this further and
replacing the Travis/Yetus build system.
Some data:
- In its current configuration, a Travis build that doesn't fail takes
around 70 minutes.
- Travis usually fai
ld suggest moving everything into one
> place. In the case of Github Actions, you can also run it easily locally:
> https://github.com/nektos/act
>
> Cheers, Fokko
>
>
> Op zo 20 dec. 2020 om 06:05 schreef Michael A. Smith :
>
> > I created a PR to implement our
d doing it all in the one PR?
>
> Cheers, Fokko
>
>
> Op zo 20 dec. 2020 om 06:05 schreef Michael A. Smith :
>
> > I created a PR to implement our tests in GitHub actions. I'd like to
> > know if other folks are interested in me pursuing this further and
> >
The commit log for branch-1.10 says "Preparing for 1.10.2
development", but I can't indicate in Jira that AVRO-3006 will be in
that release. Is that release still going to happen?
rd.)
Thanks,
Michael
On Sun, Dec 20, 2020 at 2:58 PM Michael A. Smith wrote:
>
> On Sun, Dec 20, 2020 at 6:13 AM Driesprong, Fokko
> wrote:
> >
> > Hi Michael,
> >
> > Thanks for bringing this up. I think it would be a great idea. I don't have
> >
decisions.
Let's close the vote at 2021-01-10 23:59:59 UTC.
On Mon, Jan 4, 2021 at 5:19 AM Ismaël Mejía wrote:
>
> +1 good idea! Can you please open the vote Michael
>
> Do we have multiple-python version tests? I suppose this will be
> easier to do now with the move to github
On Mon, Jan 4, 2021 at 4:57 AM Ismaël Mejía wrote:
>
> Excellent work / idea / development. 2021 starting great !
>
> I really like the idea of devs not having to wait for the all
> languages build to have feedback earlier, but we probably need an
> extra action for interop tests and that should m
gt; > >
> > > I would expect there to be an AVRO JIRA and/or a commit for every time
> we
> > > "officially" drop support for a version (at the very least to update
> the
> > > documentation), which would keep the mailing list up to date.
> > &
+1 (non-binding)
Does someone know how much effort it would be to add consistent build.sh
features to the rust implementation to ensure that the fundamental dev
process is the same across langs?
Less important, but nice to have: interop tests.
On Mon, May 24, 2021 at 12:34 Micah Kornfield wrote
I wonder if I could get a review of this pull request
https://github.com/apache/avro/pull/1270 from the larger avro dev
community.
One thing I noticed when adding type hints to python avro is that some
of our CLI tooling supports output to standardio, but standardio is
really text, not binary. I h
o a terminal, I can see an argument
> for attempting to encode data as text, since ttys usually dont handle
> non-text data well. You could use the Python standard library’s os.isatty
> function to detect whether stdout (or stderr) are connected to a terminal.
>
> On Fri, Jun 25,
I’m generally in favor of linear commits iff the committers can be trusted
to follow good git hygiene in general, like with small, proprietary
projects with strong leadership.
With Avro, with its variegated multilang repo and commits coming from the
community at large, I’m not sure if linear-rebas
ns < 2.0, at least
- As long as PYPI is counting python 3.4 downloads at > 1000/month
I move that we consider Python 3.4 and up to the latest release of Python 3
(currently 3.7) officially supported. If I don't hear any objections by
Saturday, I'll set the trove classifiers to specify those versions in
https://github.com/apache/avro/pull/347.
-Michael A. Smith (kojiro/kojiromike)
PS: please kindly let me know if I'm not following some proper procedure.
Now that the Yetus/Travis integration is running (yay), I hope it's not
premature to talk about static analysis tools, or as they're sometimes
called "automated code review".
Correct me if I have it wrong, but I believe our Yetus/Travis integration
is focused on running the handwritten test cases
f Zoltan Farkas
> :
>
> > +1 for static analysis.
> >
> > here is what codacy looks like on the avro fork I use:
> > https://app.codacy.com/project/zolyfarkas/avro/dashboard
> >
> >
> > —Z
> >
> >
> > > On Nov 7, 2018, at 10:01
Hi, Piotr,
Thanks for posting this for discussion.
In my work projects we use Python 3.6, 3.7, and (cough) 2.7. So it won’t
hurt me directly if Avro doesn’t support Python 3.4 anymore. However,
avro-py3 is a library, so wide version support is appropriate in my opinion.
Python still supports 3.4
I’m against this proposal. Sure, recursion adds complexity, but recursive
types are also extremely powerful and one of the most interesting features
of a tool like this. I have been experimenting in the other direction;
considering a way to compose avro schema descriptions in avro. Recursion is
cru
Thanks for doing that. It was very needed.
Can we automate doing this somehow.
On Thu, Nov 29, 2018 at 17:52 Ismaël Mejía wrote:
> Hello,
>
> I tagged all open PRs in github using the Label feature and the
> respective languages as part of the effort to get more reviews done.
> Hopefully people
ularity of JSON and the fact that Avro includes
> > support for converting it, I think it makes sense to continue allowing
> > recursive schemas.
> >
> > On Fri, Nov 30, 2018 at 2:12 PM Michael A. Smith
> > wrote:
> >
> > > I’m against this proposal. Sure,
Hi, Avro devs, it's time to wake this thread up for a checkpoint.
I glanced at pypi stats today and it looks like 3.4 downloads are usually
below 1000. More importantly, Python has already EOL'ed python 3.4. Do we
want to consider python 3.4 support officially dropped as of the 1.9
release?
That
za 4 mei 2019 om 20:47 schreef Rajkumar Natarajan <
> raj.cs@gmail.com
> > >
> >
> >> +1
> >>
> >> On Sat, May 4, 2019, 2:37 PM sajuukk wrote:
> >>
> >> > +1
> >> >
> >> > W dniu 04.05.2019 o 16:10, Mic
+1
On Wed, May 8, 2019 at 15:45 Driesprong, Fokko wrote:
> Hi everyone,
>
> Since the last release of Apache Avro 1.8.2 on May 31, 2017. Two years
> later,
> I'm thrilled to propose the following RC to be released as official Apache
> Avro 1.9.0 release.
>
> The commit id is 3c76495e9524ef322726
If anyone out there is comfortable reviewing Python, please consider
reviewing the list of open python and python3 PRs. Fokko has been more than
responsive, but it'd be better if we could get more eyes on this stuff.
https://github.com/apache/avro/labels/Python3
https://github.com/apache/avro/labe
I am working on making all the py and py3 code consistent with
https://github.com/python/black, but once done it’d be great if we could
keep it consistent. I will look into adding hooks and stuff for
yetus/TravisCI, but is there a way to have an automation that can
periodically do all the formattin
> > >
> > > I don't think that such a CI service exists, and I also think it is a
> bad
> > > idea. The author should format his code on forehand.
> > >
> > > I've also looked in setting up Dependabot for Avro, but this is against
> > t
t; command:
> > black --check --diff .
> > will throw a non-zero exit code when there is something to format.
> >
> > Cheers, Fokko
> >
> >
> >
> > Op wo 29 mei 2019 om 04:04 schreef Michael A. Smith <
> mich...@smith-li.com>:
> >
> > &
There's some not-insignificant complexity in the lang/py codebase to
support derelict versions of Python. There are polyfills for json, structs,
a whole "StoppableHTTPServer" in avro.tool.
I created AVRO-2445 and will start removing this stuff now, but wanted to
bounce the idea around the list in
into Python2.7 in general,
> since
> > this version is EOL after this year.
> >
> > Cheers, Fokko
> >
> > Op ma 24 jun. 2019 om 03:20 schreef Michael A. Smith <
> mich...@smith-li.com>:
> >
> > > There's some not-insignificant com
The webpage at https://avro.apache.org/version_control.html says
> The Avro community welcomes pull requests, but please create an issue in
> Avro's issue tracker for your bug report or contribution as well.
Then in our PR template we request that folks link back to Jira.
GitHub recently added
obably not *ideal* for
> python: unlike Java code using a specific record, an expected datum
> due to a bad logical type in the schema won't be detected at compile
> time...
>
> Michael A. Smith suggested making this a configurable warning so the
> user can control whether the misconfiguration is shown, ignored or
> causes failure -- sound fine to everyone?
>
> Best regards, Ryan
>
fields. But that
can't be right -- default is crucial for readers, and two schema
differing only on by a default are certainly different schema and
ought to have different fingerprints.
Did I miss something in reading the spec, or is this a gap? How should
I interpret the spec in implementing parsing canonical form for record
fields. Specifically, should the canonical form of a record field
preserve its order and default values in the [STRIP] rule, and if so,
where do those things go in the [ORDER] rule?
Thanks,
Michael A. Smith
sistent length, how could users benefit from it?
Thanks,
Michael A. Smith
Another two things I'm struggling to understand in PCF are the strings and
integers rules
- [STRINGS] For all JSON string literals in the schema text, replace any
escaped characters (e.g., \u escapes) with their UTF-8 equivalents.
- [INTEGERS] Eliminate quotes around and any leading z
ronous avro IPC transceiver in Python 3, please reply so we can
work out how to proceed.
Thanks,
Michael A. Smith
JIRA doesn't have a lot of sense.
>
> Does the BSON example imply that it would be useful to get the Avro
> length of a datum given a schema?
>
> Roughly: `len(my_schema.from_datum({"hello": "world"})) == 22` ? It
> doesn't seem quite right either!
little significant impact.
>
> Ryan
>
>
>
> On Tue, Jun 25, 2019 at 1:22 PM Michael A. Smith
> wrote:
> >
> > Inline…
> >
> > On Tue, Jun 25, 2019 at 05:03 Ismaël Mejía wrote:
> >
> > > Probably is a good idea that we publish our poli
Congratulations and thanks for the great work, Ryan!
On Tue, Dec 17, 2019 at 04:43 Driesprong, Fokko
wrote:
> Folks,
>
> The Project Management Committee (PMC) for Apache Avro has invited Ryan
> Skraba to become a committer and we are pleased to announce that he has
> accepted. Ryan is actively
Hi, I've finished building out a unified python approach in lang/py.
It passes our full Yetus tests in cpython 2.7 and 3.5. I also tested
it and passed locally in 3.6, 3.7 and 3.8 as well as pypy 7.2.0 for
both 2.7 and 3.6.
The pull request is here: https://github.com/apache/avro/pull/744
I know
rough pass through the types of changes and cleanup, and I'm
> pretty happy :D I'll try to get more thorough pass done, but (indeed)
> I probably won't have a lot of time between now and the new year.
>
> All my best, Ryan
>
> On Fri, Dec 20, 2019 at 12:36 AM Mi
t Python2 for a while, it is still part of the CI. Supporting only
> higher versions of Python, such as 3.6, allows us to use new features, such
> as type annotations.
>
> Cheers, Fokko
>
> Op zo 5 jan. 2020 om 18:44 schreef Michael A. Smith >:
>
> > Hi! Given that P
would like to do for Avro in the future? For example,
> releasing avro-python3 version 1.10.0 with the sole message of having to
> import the avro package? Would like to get your opinion on this.
>
> Cheers, Fokko
>
> Op ma 6 jan. 2020 om 13:32 schreef Michael A. Smith >:
So far none of my python2/3 changes have been targeting 1.9. They're
currently just in master. It would be great if someone could cherry pick
them. I'm away this weekend, but happy to help via phone or more directly
next week if it turns complex.
Best regards,
Mike
On Sat, Jan 11, 2020 at 07:39 D
p the API compatible.
>
> Cheers, Fokko
>
> Op za 11 jan. 2020 om 13:51 schreef Michael A. Smith >:
>
> > So far none of my python2/3 changes have been targeting 1.9. They're
> > currently just in master. It would be great if someone could cherry pick
> > them. I'
some
not. Those changes are wide-ranging and not easy to cherry pick. They don't
affect functionality directly, but if I skip them I don't think the tests
can pass.
Does anyone with a better understanding of the 1.9 chronology want to give
it a shot?
On Mon, Jan 13, 2020 at 06:57 M
artifacts.
> 5. Can I get edit permissions on the Avro confluence wiki?
>
> Is 2,3,4 necessary or does someone already with permissions do the release?
>
> All my best! Ryan
>
>
> On Fri, Jan 17, 2020 at 1:47 AM Michael A. Smith wrote:
> >
> > I may have bitten of
Hi, Cris,
Good to see you around these parts. (Idk if you remember me, but we
worked together a bit on Plone back in the day.) I just tried the same
thing and wasn't able to reproduce the issue. Can you check if the
openjdk:11-stretch image that the Dockerfile is based on has the
digest sha256:04b
I run `docker image ls` I find this entry for openjdk:11-stretch:
>
> openjdk
> 11-stretch193af7392c2e11 days ago 606MB
>
> I am still getting the same error when trying to use the `./build.sh
> docker` command. So this is (at least on my end) 100% r
By the way, are you planning to work on the python implementation? If
so, a workaround to your current troubles would be not to use docker
for now. lang/py has no runtime dependencies. You can cd in there and
run tox to run the tests.
On Thu, Feb 13, 2020 at 12:44 PM Cris Ewing wrote:
>
> Greetin
ris Ewing
> > wrote:
> >
> > > I followed this approach and called dig from my host machine. Then
> > > realized that dig meant DNS was implicated and turned off my company
> VPN.
> > > Re-ran `./build.sh docker` and it succeeded.
> >
+1 It's a great idea.
On Fri, Feb 14, 2020 at 4:20 AM Ismaël Mejía wrote:
>
> Now that Avro 1.9.2 was released I wanted to propose a sort of roadmap for
> the
> next release. We already have accumulated a good chunk of new features and
> fixes
> that can be released as Avro 1.10.0. I would like
I think we should be packaging avro for python using wheels, and I've
said as much in AVRO-2399, but I'm stumbling on some stuff.
The first stumbling block is that avro has artifacts in ./share that
it wants in the package, but the package root starts at ./lang/py. We
work around this with a fair
A while back I opened
https://issues.apache.org/jira/browse/INFRA-19615 to see if Apache
Infrastructure can help us do something constructive with test results
in the form of something standard, like a nice result viewer for
junit.xml artifacts. One question that was asked in the ticket was
> The
In https://github.com/apache/avro/pull/830 I propose that we offer
users the option to maintain Python's current behavior of allowing
spaces in enum symbols. In this implementation, the default behavior
is more spec-compliant, but users can choose to go back to the way it
was. Since Python has neve
I noticed that the Windows build fails sometimes, and that it seems to
have to do with platform conditions and not changes to the avro
codebase. Here's the build history:
https://travis-ci.org/apache/avro/builds
and at the time I write this, the latest build has failed in Windows
(1808.3) https:/
Hi, Sandeep,
If you want to run just the unit tests for python, you can use tox. Just
running `tox` by itself should be sufficient if you have at least one of
the supported versions of python installed.
I'll take a look at getting those docs updated.
On Wed, Apr 22, 2020 at 19:50 Sandeep Narayan
r multiple
languages is what it takes to fix that, then it's probably for the best.
If we do go down that road, I'd like to see us make the build process
extremely smooth.
All the best,
Michael A. Smith
On Tue, Apr 28, 2020 at 04:01 Ismaël Mejía wrote:
> Huge +1 to recover the Avr
Thanks, Martin,
It seems like since that PR isn't merged yet, and it would be
complicated to add all the Sphinx stuff to it, I should merge my
changes first, and then add the Python stuff to #2187 after that.
Does that seem reasonable?
On Thu, Jul 20, 2023 at 2:30 AM Martin Grigorov wrote:
>
>
OK, I've merged that PR and have made suggested changes to #2187.
Please let me know how I can help.
On Thu, Jul 20, 2023 at 11:27 AM Martin Grigorov wrote:
>
> On Thu, 20 Jul 2023 at 17:47, Michael A. Smith wrote:
>
> > Thanks, Martin,
> >
> > It seems like sin
gate this, and I'm definitely on the low end
> 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
> > wrote:
> &
all tox manually.
On Fri, Jul 21, 2023 at 5:56 PM Martin Grigorov wrote:
>
> 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 cherr
uff (probably macOS things) atm.
On Fri, Jul 21, 2023 at 5:56 PM Martin Grigorov
wrote:
>
> 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 c
Please take a look at AVRO-3816. I'm proposing a backwards
incompatible change to the python schema implementation. So far I have
a PR in draft that I believe _is_ backwards-compatible, but is just a
step on the way - it doesn't solve the problem entirely.
I'd like to get to the following advantag
The spec says one of the steps to get parsing canonical form is
> [STRIP] Keep only attributes that are relevant to parsing data, which are:
> type, name, fields, symbols, items, values, size. Strip all others (e.g., doc
> and aliases).
and indeed, we strip the default from an EnumSchema. But i
as deprecated for the length of one major release
> before removing them?
>
> I have no objection to improving the Python API :D Your PR is pretty
> readable!
>
> All my best, Ryan
>
> On Sat, Jul 29, 2023 at 2:02 AM Michael A. Smith wrote:
> >
> > Pleas
I found I'm still a little confused at how using aliases to correct
invalid names should work. Maybe you can define an alias that is an
invalid name, but having done so, can you use it? I tried this schema
in both the Python and Java implementations.
{"type":"record","name":"AliasReferenceExample"
t; On Fri, 18 Aug 2023 at 04:32, Michael A. Smith
> wrote:
>
> > I found I'm still a little confused at how using aliases to correct
> > invalid names should work. Maybe you can define an alias that is an
> > invalid name, but having done so, can you use it? I tried
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.
Python 3.8 compatibility has been gone from pypy since 2023-06-16.
http
+1
We could dig up the old vote about our strategy here, but I'm sure there's
no conflict.
On Wed, Oct 9, 2024 at 12:11 Oscar Westra van Holthe - Kind <
os...@westravanholthe.nl> wrote:
> +1 from me as well. The maintainers argument Martin mentioned is a strong
> one.
>
> Upgrading the Python ve
I'll knock that out, sorry. I was waiting for GH to work all the quirks out
of 24.04 and then life happened. It should be good now.
https://github.com/apache/avro/pull/3359
On Thu, Apr 17, 2025 at 1:07 PM Ryan Skraba wrote:
> I did a cowboy commit and merged my own PR, not the best practice
> b
[
https://issues.apache.org/jira/browse/AVRO-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494604#comment-16494604
]
Michael A. Smith commented on AVRO-2174:
Linked to AVRO-1725, which descr
Michael A. Smith created AVRO-2183:
--
Summary: Nameless schema should raise AttributeError when
attempting to access name
Key: AVRO-2183
URL: https://issues.apache.org/jira/browse/AVRO-2183
Project
[
https://issues.apache.org/jira/browse/AVRO-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16494624#comment-16494624
]
Michael A. Smith commented on AVRO-1880:
I agree, for whatever my opinio
[
https://issues.apache.org/jira/browse/AVRO-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16629717#comment-16629717
]
Michael A. Smith commented on AVRO-2196:
I can confirm this error using a c
Michael A. Smith created AVRO-2230:
--
Summary: ./build.sh test fails in c++
Key: AVRO-2230
URL: https://issues.apache.org/jira/browse/AVRO-2230
Project: Avro
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AVRO-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633020#comment-16633020
]
Michael A. Smith commented on AVRO-2229:
Did you not run into a java test fai
[
https://issues.apache.org/jira/browse/AVRO-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633021#comment-16633021
]
Michael A. Smith commented on AVRO-2203:
I got a 404 when I tried to access
Michael A. Smith created AVRO-2234:
--
Summary: Use native MappingProxyType instead of hand-written
ImmutableDict
Key: AVRO-2234
URL: https://issues.apache.org/jira/browse/AVRO-2234
Project: Avro
[
https://issues.apache.org/jira/browse/AVRO-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael A. Smith updated AVRO-2230:
---
Summary: ./build.sh test fails in c++ due to assignment to const (was:
./build.sh test fails
[
https://issues.apache.org/jira/browse/AVRO-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael A. Smith resolved AVRO-2230.
Resolution: Fixed
Fixed in a patch intended for AVRO-2209
> ./build.sh test fails i
[
https://issues.apache.org/jira/browse/AVRO-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516396#comment-17516396
]
Michael A. Smith commented on AVRO-3476:
[~ladoe00] hi, thanks for reporting.
[
https://issues.apache.org/jira/browse/AVRO-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael A. Smith updated AVRO-3261:
---
Description: boto3 python library has [s3
get_object|https://boto3.amazonaws.com/v1
[
https://issues.apache.org/jira/browse/AVRO-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17516399#comment-17516399
]
Michael A. Smith commented on AVRO-3261:
If your avro file is an [ob
[
https://issues.apache.org/jira/browse/AVRO-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael A. Smith updated AVRO-3476:
---
Description:
Even though [they are present in the
spec|https://avro.apache.org/docs/1.11.0
[
https://issues.apache.org/jira/browse/AVRO-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael A. Smith updated AVRO-3476:
---
Description:
Even though [they are present in the
spec|https://avro.apache.org/docs/1.11.0
[
https://issues.apache.org/jira/browse/AVRO-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561791#comment-17561791
]
Michael A. Smith commented on AVRO-3504:
[~izveigor] I noticed your PR was cl
[
https://issues.apache.org/jira/browse/AVRO-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155408#comment-17155408
]
Michael A. Smith commented on AVRO-2747:
Yep, a release is being published
[
https://issues.apache.org/jira/browse/AVRO-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155513#comment-17155513
]
Michael A. Smith commented on AVRO-2768:
Is this still an issue? The linked
Michael A. Smith created AVRO-2892:
--
Summary: Avro should provide codec implementations for Python
Key: AVRO-2892
URL: https://issues.apache.org/jira/browse/AVRO-2892
Project: Apache Avro
Michael A. Smith created AVRO-2893:
--
Summary: Isolate Exception Classes to Simplify Import Graph
Key: AVRO-2893
URL: https://issues.apache.org/jira/browse/AVRO-2893
Project: Apache Avro
[
https://issues.apache.org/jira/browse/AVRO-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael A. Smith reassigned AVRO-2893:
--
Assignee: Michael A. Smith
> Isolate Exception Classes to Simplify Import Gr
1 - 100 of 484 matches
Mail list logo
