Re: [jira] [Commented] (AVRO-1334) Java: update dependencies for 1.7.5
1.7.5 uses Jackson 1.9.13 (the latest 1.x.x). 2.x is in a different package namespace and does not conflict with users. On 8/8/13 9:24 AM, Doug Cutting cutt...@apache.org wrote: On Wed, Aug 7, 2013 at 7:27 PM, Jeremy Kahn troc...@trochee.net wrote: I'd really like to see Jackson upgraded Scott? Any thoughts? Will upgrading versions of dependencies in a minor, bugfix release create any compatibility problems? Doug
[jira] [Updated] (AVRO-1360) C++ Resolving decoder is not working when reader schema has more fields than writer schema
[
https://issues.apache.org/jira/browse/AVRO-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramana Suvarapu updated AVRO-1360:
--
Attachment: writer.json
reader.json
C++ Resolving decoder is not working when reader schema has more fields than
writer schema
--
Key: AVRO-1360
URL: https://issues.apache.org/jira/browse/AVRO-1360
Project: Avro
Issue Type: Bug
Components: c++
Affects Versions: 1.7.4
Reporter: Ramana Suvarapu
Attachments: reader.json, writer.json
When reader schema has more number of fields than writer schema, C++
implementation of resolving decoder is throwing exception throwing exception
Don't know how to handle excess fields for reader.” with out checking
whether fields are optional or fields have default values.
Attached are reader and writer schemas. Record in reader schema has 2
additional fields than writer schema. One field is required field but it has
default value and another one is optional field (union of null and string).
Since one has default value and another is optional both reader and writer
schemas are supposed to be compatible.
{name: defaultField, type: string, default: DEFAULT,
declared:true},
{name: optionalField, type: [string, null],declared:true},
main()
{
avro::ValidSchema readerSchema = load(reader.json);
avro::ValidSchema writerSchema = load(writer.json);
avro::DecoderPtr d = avro::resolvingDecoder(writerSchema,
readerSchema,avro::binaryDecoder());
}
But when I tried to create resolving decoder, I am getting Don't know how to
handle excess fields for reader.” But Java implementation works.
Can you please let us know if there are any other limitations with c++
implementation of ResolvingDecoder? We are planning to use it in our project
and we want to make sure it works as per avro specification.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AVRO-1360) C++ Resolving decoder is not working when reader schema has more fields than writer schema
Ramana Suvarapu created AVRO-1360:
-
Summary: C++ Resolving decoder is not working when reader schema
has more fields than writer schema
Key: AVRO-1360
URL: https://issues.apache.org/jira/browse/AVRO-1360
Project: Avro
Issue Type: Bug
Components: c++
Affects Versions: 1.7.4
Reporter: Ramana Suvarapu
Attachments: reader.json, writer.json
When reader schema has more number of fields than writer schema, C++
implementation of resolving decoder is throwing exception throwing exception
Don't know how to handle excess fields for reader.” with out checking whether
fields are optional or fields have default values.
Attached are reader and writer schemas. Record in reader schema has 2
additional fields than writer schema. One field is required field but it has
default value and another one is optional field (union of null and string).
Since one has default value and another is optional both reader and writer
schemas are supposed to be compatible.
{name: defaultField, type: string, default: DEFAULT,
declared:true},
{name: optionalField, type: [string, null],declared:true},
main()
{
avro::ValidSchema readerSchema = load(reader.json);
avro::ValidSchema writerSchema = load(writer.json);
avro::DecoderPtr d = avro::resolvingDecoder(writerSchema,
readerSchema,avro::binaryDecoder());
}
But when I tried to create resolving decoder, I am getting Don't know how to
handle excess fields for reader.” But Java implementation works.
Can you please let us know if there are any other limitations with c++
implementation of ResolvingDecoder? We are planning to use it in our project
and we want to make sure it works as per avro specification.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Avro release 1.7.5 (rc0)
Can some other PMC members please vote on this? Thanks, Doug On Fri, Aug 9, 2013 at 11:48 AM, Doug Cutting cutt...@apache.org wrote: +1 Downloaded sources, ran tests, checked licensing, validated checksums signatures, compared to subversion tag. All looks good. Doug On Thu, Aug 8, 2013 at 9:29 AM, Doug Cutting cutt...@apache.org wrote: I have created a candidate build for Avro release 1.7.5. Changes are listed at: http://s.apache.org/Avro175 Please download the sources, check them, and vote. http://people.apache.org/~cutting/avro-1.7.5-rc0/ The Maven staging repository is at: https://repository.apache.org/content/repositories/orgapacheavro-076/ Thanks in advance for voting! Doug
[jira] [Updated] (AVRO-1126) Upgrade to Jackson 2+
[
https://issues.apache.org/jira/browse/AVRO-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-1126:
---
Fix Version/s: 1.8.0
Upgrade to Jackson 2+
-
Key: AVRO-1126
URL: https://issues.apache.org/jira/browse/AVRO-1126
Project: Avro
Issue Type: Task
Components: java
Reporter: James Tyrrell
Priority: Critical
Fix For: 1.8.0
Quite annoyingly with Jackson 2+ the base package name has changed from
org.codehaus.jackson to com.fasterxml.jackson so in addition to changing the
dependencies from:
{code:xml}
dependency
groupIdorg.codehaus.jackson/groupId
artifactIdjackson-core-asl/artifactId
version${jackson.version}/version
/dependency
dependency
groupIdorg.codehaus.jackson/groupId
artifactIdjackson-mapper-asl/artifactId
version${jackson.version}/version
/dependency
{code}
to:
{code:xml}
dependency
groupIdcom.fasterxml.jackson.core/groupId
artifactIdjackson-core/artifactId
version${jackson.version}/version
/dependency
dependency
groupIdcom.fasterxml.jackson.core/groupId
artifactIdjackson-databind/artifactId
version${jackson.version}/version
/dependency
{code}
the base package in the code needs to be updated. More info can be found
[here|http://wiki.fasterxml.com/JacksonUpgradeFrom19To20], I am happy to do
the work just let me know what is preferable i.e. should I just attach a
patch to this issue?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AVRO-1182) DataFileReader missing seek, sync methods
[ https://issues.apache.org/jira/browse/AVRO-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737458#comment-13737458 ] Daniel Russel commented on AVRO-1182: - I'm uploading an updated patch that adds tests that hit the split sync code (and pass). DataFileReader missing seek, sync methods - Key: AVRO-1182 URL: https://issues.apache.org/jira/browse/AVRO-1182 Project: Avro Issue Type: Improvement Components: c++ Affects Versions: 1.7.3 Reporter: Daniel Russel Attachments: add_seek, with_partial_sync_test The DataFileReader is missing the seek and sync methods that are found in the java version making it hard to navigate a file except in a linear fashion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AVRO-1182) DataFileReader missing seek, sync methods
[ https://issues.apache.org/jira/browse/AVRO-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Russel updated AVRO-1182: Attachment: with_partial_sync_test DataFileReader missing seek, sync methods - Key: AVRO-1182 URL: https://issues.apache.org/jira/browse/AVRO-1182 Project: Avro Issue Type: Improvement Components: c++ Affects Versions: 1.7.3 Reporter: Daniel Russel Attachments: add_seek, with_partial_sync_test The DataFileReader is missing the seek and sync methods that are found in the java version making it hard to navigate a file except in a linear fashion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AVRO-1182) DataFileReader missing seek, sync methods
[ https://issues.apache.org/jira/browse/AVRO-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Russel updated AVRO-1182: Attachment: (was: add_seek) DataFileReader missing seek, sync methods - Key: AVRO-1182 URL: https://issues.apache.org/jira/browse/AVRO-1182 Project: Avro Issue Type: Improvement Components: c++ Affects Versions: 1.7.3 Reporter: Daniel Russel Attachments: with_partial_sync_test The DataFileReader is missing the seek and sync methods that are found in the java version making it hard to navigate a file except in a linear fashion. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
