The issues in the yaml file are every comment done on every issue or
pull requests on github (notice that the issues part probably won't
apply to us since we use JIRA to track issues).
Currently we receive ALL JIRA notifications into dev@ we can change
that us well since it probably makes
Consensus is a big word for this case.
I am not really convinced this will get us to a better state for the reasons
already exposed before. In my opinion we are having a BIG case of
wishful thinking.
We had a really hard time to put together a new release for 1.9.0 and one of the
reasons was the
Other alternative (probably the cleanest is to let dev@ only for
discussion and issues for all the JIRA/github action. The tradeoff
there is that people subscribed to dev@ only may miss part of the
action (+ it is not backwards compatible with our archives) but it is
clearly an option too.
On
[
https://issues.apache.org/jira/browse/AVRO-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100559#comment-17100559
]
Ryan Skraba commented on AVRO-2278:
---
Argh – the change in the PR is _better_ (in my opinion) but
RyanSkraba commented on pull request #864:
URL: https://github.com/apache/avro/pull/864#issuecomment-624503370
I did an experiment with our existing code base and [left a
[
https://issues.apache.org/jira/browse/AVRO-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100697#comment-17100697
]
Zoltan Farkas edited comment on AVRO-2278 at 5/6/20, 11:48 AM:
---
[~rskraba]
[
https://issues.apache.org/jira/browse/AVRO-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100697#comment-17100697
]
Zoltan Farkas edited comment on AVRO-2278 at 5/6/20, 11:49 AM:
---
[~rskraba]
[
https://issues.apache.org/jira/browse/AVRO-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100864#comment-17100864
]
Zoltan Farkas commented on AVRO-2278:
-
There is basically one behavior that we are changing here
[
https://issues.apache.org/jira/browse/AVRO-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Farkas updated AVRO-1607:
Description:
In SpecificData.getClass, line 164:
{code}
case UNION:
List types =
This sounds good to me! The "issues" in the yaml are the GitHub
issues, which are disabled in github right?
Any opinions on moving JIRA notifications from j...@apache.org to
issues@ as well? That's what I would expect!
I guess this would make little difference to me in practice since I
would
[
https://issues.apache.org/jira/browse/AVRO-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100697#comment-17100697
]
Zoltan Farkas commented on AVRO-2278:
-
[~rskraba] what about controlling this behavior with a System
[
https://issues.apache.org/jira/browse/AVRO-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Farkas resolved AVRO-1580.
-
Resolution: Fixed
> Use newer version of surefire, 2.17 instead of 2.12
>
[
https://issues.apache.org/jira/browse/AVRO-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100790#comment-17100790
]
Zoltan Farkas commented on AVRO-1603:
-
One other reason for this is to instead of having the avro
[
https://issues.apache.org/jira/browse/AVRO-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100833#comment-17100833
]
Ryan Skraba commented on AVRO-2278:
---
I think feature flags or system properties are a good tool! We've
[
https://issues.apache.org/jira/browse/AVRO-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101022#comment-17101022
]
ASF subversion and git services commented on AVRO-2815:
---
Commit
[
https://issues.apache.org/jira/browse/AVRO-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fokko Driesprong resolved AVRO-2815.
Fix Version/s: 1.10.0
Resolution: Fixed
> Update Python Documentation on how to test
[
https://issues.apache.org/jira/browse/AVRO-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fokko Driesprong reassigned AVRO-2815:
--
Assignee: Fokko Driesprong
> Update Python Documentation on how to test
>
maxfield-riley removed a comment on pull request #492:
URL: https://github.com/apache/avro/pull/492#issuecomment-624736873
Do we have a fix for this in the avrogen tool so we can properly build
POCO's from avsc files?
Currently the avrogen tool generates
`
"type": {
maxfield-riley edited a comment on pull request #492:
URL: https://github.com/apache/avro/pull/492#issuecomment-624736873
Do we have a fix for this in the avrogen tool so we can properly build
POCO's from avsc files?
Currently the avrogen tool generates
`
"type": {
maxfield-riley edited a comment on pull request #492:
URL: https://github.com/apache/avro/pull/492#issuecomment-624736873
Do we have a fix for this in the avrogen tool so we can properly build
POCO's from avsc files?
Currently the avrogen tool generates
`
"type": {
maxfield-riley commented on pull request #492:
URL: https://github.com/apache/avro/pull/492#issuecomment-624736873
Do we have a fix for this in the avrogen tool so we can properly build
POCO's from avsc files?
This is an
[
https://issues.apache.org/jira/browse/AVRO-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100978#comment-17100978
]
Ryan Skraba commented on AVRO-2808:
---
Ah! Yes, that sounds like a good change to clarify what is wrong
[
https://issues.apache.org/jira/browse/AVRO-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Skraba resolved AVRO-2805.
---
Resolution: Cannot Reproduce
> Reflection-based schema not loading types
>
[
https://issues.apache.org/jira/browse/AVRO-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100874#comment-17100874
]
Ryan Skraba commented on AVRO-2808:
---
I think this should be the expected behaviour for non-static inner
[
https://issues.apache.org/jira/browse/AVRO-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100968#comment-17100968
]
Ryan Skraba commented on AVRO-2817:
---
For info: it looks like the schema is invalid: the default value
[
https://issues.apache.org/jira/browse/AVRO-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100882#comment-17100882
]
Andy Le commented on AVRO-2808:
---
[~rskraba] nice to see you here.
> I think this should be the expected
[
https://issues.apache.org/jira/browse/AVRO-2775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17100865#comment-17100865
]
Ryan Skraba commented on AVRO-2775:
---
Hello! Just a quick point of view on this -- if I understand
maxfield-riley edited a comment on pull request #492:
URL: https://github.com/apache/avro/pull/492#issuecomment-624736873
Do we have a fix for this in the avrogen tool so we can properly build
POCO's from avsc files?
Currently the avrogen tool generates
`
"type": {
Fokko commented on pull request #870:
URL: https://github.com/apache/avro/pull/870#issuecomment-624776170
Thanks for the review @kojiromike @RyanSkraba
This is an automated message from the Apache Git Service.
To respond to
[
https://issues.apache.org/jira/browse/AVRO-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101021#comment-17101021
]
ASF subversion and git services commented on AVRO-2815:
---
Commit
[
https://issues.apache.org/jira/browse/AVRO-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101052#comment-17101052
]
Hudson commented on AVRO-2815:
--
SUCCESS: Integrated in Jenkins build AvroJava #858 (See
31 matches
Mail list logo
