[jira] [Assigned] (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
]
Thiruvalluvan M. G. reassigned AVRO-1360:
-
Assignee: Thiruvalluvan M. G.
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
Assignee: Thiruvalluvan M. G.
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] [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
]
Thiruvalluvan M. G. updated AVRO-1360:
--
Attachment: AVRO-1360.patch
This patch enables AVRO C++ to handle schema resolution.
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
Assignee: Thiruvalluvan M. G.
Attachments: AVRO-1360.patch, 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] [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
]
Thiruvalluvan M. G. updated AVRO-1360:
--
Status: Patch Available (was: Open)
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
Assignee: Thiruvalluvan M. G.
Attachments: AVRO-1360.patch, 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] [Updated] (AVRO-1363) C# UnionSchema fails to parse the the unions with same type names with different namespaces
[
https://issues.apache.org/jira/browse/AVRO-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramana Suvarapu updated AVRO-1363:
--
Attachment: reader.avpr
C# UnionSchema fails to parse the the unions with same type names with
different namespaces
---
Key: AVRO-1363
URL: https://issues.apache.org/jira/browse/AVRO-1363
Project: Avro
Issue Type: Bug
Components: csharp
Affects Versions: 1.7.4
Reporter: Ramana Suvarapu
Attachments: reader.avpr
C# Union schema is unable to handle same type names with different
namespaces. It's throwing SchemaParseException(Duplicate type in union:
...) exception.
In the below code, key of uniqueSchemas should be FullName of the type which
is similar to Java implementation.
internal static UnionSchema NewInstance(JArray jarr, PropertyMap props,
SchemaNames names, string encspace)
{
ListSchema schemas = new ListSchema();
IDictionarystring, string uniqueSchemas = new
Dictionarystring, string();
foreach (JToken jvalue in jarr)
{
Schema unionType = Schema.ParseJson(jvalue, names, encspace);
if (null == unionType)
throw new SchemaParseException(Invalid JSON in union +
jvalue.ToString());
string name = unionType.Name;
if (uniqueSchemas.ContainsKey(name))
throw new SchemaParseException(Duplicate type in union:
+ name);
uniqueSchemas.Add(name, name);
schemas.Add(unionType);
}
return new UnionSchema(schemas, props);
}
See the attachement to recreate the 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] [Created] (AVRO-1363) C# UnionSchema fails to parse the the unions with same type names with different namespaces
Ramana Suvarapu created AVRO-1363:
-
Summary: C# UnionSchema fails to parse the the unions with same
type names with different namespaces
Key: AVRO-1363
URL: https://issues.apache.org/jira/browse/AVRO-1363
Project: Avro
Issue Type: Bug
Components: csharp
Affects Versions: 1.7.4
Reporter: Ramana Suvarapu
Attachments: reader.avpr
C# Union schema is unable to handle same type names with different namespaces.
It's throwing SchemaParseException(Duplicate type in union: ...) exception.
In the below code, key of uniqueSchemas should be FullName of the type which is
similar to Java implementation.
internal static UnionSchema NewInstance(JArray jarr, PropertyMap props,
SchemaNames names, string encspace)
{
ListSchema schemas = new ListSchema();
IDictionarystring, string uniqueSchemas = new Dictionarystring,
string();
foreach (JToken jvalue in jarr)
{
Schema unionType = Schema.ParseJson(jvalue, names, encspace);
if (null == unionType)
throw new SchemaParseException(Invalid JSON in union +
jvalue.ToString());
string name = unionType.Name;
if (uniqueSchemas.ContainsKey(name))
throw new SchemaParseException(Duplicate type in union:
+ name);
uniqueSchemas.Add(name, name);
schemas.Add(unionType);
}
return new UnionSchema(schemas, props);
}
See the attachement to recreate the 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] [Updated] (AVRO-1334) Java: update dependencies
[
https://issues.apache.org/jira/browse/AVRO-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated AVRO-1334:
---
Fix Version/s: (was: 1.7.5)
1.8.0
Summary: Java: update dependencies (was: Java: update dependencies
for 1.7.5)
Java: update dependencies
-
Key: AVRO-1334
URL: https://issues.apache.org/jira/browse/AVRO-1334
Project: Avro
Issue Type: Bug
Components: java
Reporter: Scott Carey
Assignee: Scott Carey
Priority: Minor
Fix For: 1.8.0
Attachments: AVRO-1334.patch
A report for mvn versions:display-property-updates on trunk --
{noformat}
[INFO] The following version properties are referencing the newest available
version:
[INFO] ${jetty.version} . 6.1.26
[INFO] ${javacc-plugin.version} 2.6
[INFO] ${velocity.version} . 1.7
[INFO] ${exec-plugin.version} 1.2.1
[INFO] The following version property updates are available:
[INFO] ${jackson.version} .. 1.8.8 - 1.9.11
[INFO] ${source-plugin.version} . 2.1.2 - 2.2.1
[INFO] ${jar-plugin.version} .. 2.3.2 - 2.4
[INFO] ${snappy.version} . 1.0.5 - 1.1.0-M3
[INFO] ${checkstyle-plugin.version} 2.8 - 2.10
[INFO] ${hadoop1.version} .. 0.20.205.0 - 1.1.2
[INFO] ${commons-compress.version} 1.4.1 - 1.5
[INFO] ${plugin-plugin.version} . 2.9 - 3.2
[INFO] ${javadoc-plugin.version} 2.8 - 2.9
[INFO] ${compiler-plugin.version} . 2.3.2 - 3.1
[INFO] ${jopt-simple.version} ... 4.1 - 4.4
[INFO] ${surefire-plugin.version} ... 2.12 - 2.14.1
[INFO] ${paranamer.version} ... 2.3 - 2.5.2
[INFO] ${netty.version} 3.4.0.Final - 4.0.0.Alpha8
[INFO] ${slf4j.version} . 1.6.4 - 1.7.5
[INFO] ${shade-plugin.version} .. 1.5 - 2.1
[INFO] ${junit.version} ... 4.10 - 4.11
{noformat}
Consider upgrades for these as well as the Apache parent and build plugins.
--
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-1336) Tests TestKeyValueWordCount and TestKeyWordCount fail due to missing files (Trevni mapreduce module)
[ https://issues.apache.org/jira/browse/AVRO-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated AVRO-1336: --- Fix Version/s: (was: 1.7.4) 1.7.6 Is this still an issue in 1.7.5? If so, perhaps we can fix it in 1.7.6. Tests TestKeyValueWordCount and TestKeyWordCount fail due to missing files (Trevni mapreduce module) Key: AVRO-1336 URL: https://issues.apache.org/jira/browse/AVRO-1336 Project: Avro Issue Type: Bug Components: trevni Affects Versions: 1.7.4 Environment: Red Hat Server 6.4 Avro 1.7.4 Maven 3.0.5 Java 1.6 (IBM or Oracle) Hadoop1 = 1.1.2 Hadoop2 = 2.0.4-alpha Reporter: Rodrigo Trujillo Assignee: Rodrigo Trujillo Fix For: 1.7.6 Attachments: fix_avro_1.7.4_trevni_build_hadoop2.patch I tried to build Avro 1.7.4 with Hadoop 2 and get the following errors in Trevni mapreduce module tests: == ... Running org.apache.trevni.avro.mapreduce.TestKeyValueWordCount Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.536 sec FAILURE! Running org.apache.trevni.avro.mapreduce.TestKeyWordCount Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.505 sec FAILURE! Running org.apache.trevni.avro.TestCases Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.671 sec Running org.apache.trevni.avro.TestWordCount Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.651 sec Results : Tests in error: testIOFormat(org.apache.trevni.avro.mapreduce.TestKeyValueWordCount): target/wc/trevniMapReduceKeyValueTest/out/part-r-0/part-0.trv (No such file or directory) testIOFormat(org.apache.trevni.avro.mapreduce.TestKeyWordCount): target/wc/trevniMapReduceKeyTest/out/part-r-0/part-0.trv (No such file or directory) Tests run: 23, Failures: 0, Errors: 2, Skipped: 0 ... == StackTraces: --- Test set: org.apache.trevni.avro.mapreduce.TestKeyValueWordCount --- Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.537 sec FAILURE! testIOFormat(org.apache.trevni.avro.mapreduce.TestKeyValueWordCount) Time elapsed: 2.029 sec ERROR! java.io.FileNotFoundException: target/wc/trevniMapReduceKeyValueTest/out/part-r-0/part-0.trv (No such file or directory) at java.io.FileInputStream.init(FileInputStream.java:124) at org.apache.trevni.InputFile.init(InputFile.java:33) at org.apache.trevni.avro.AvroColumnReader$Params.init(AvroColumnReader.java:69) at org.apache.trevni.avro.WordCountUtil.validateCountsFileGenericRecord(WordCountUtil.java:122) at org.apache.trevni.avro.mapreduce.TestKeyValueWordCount.checkOutputFormat(TestKeyValueWordCount.java:138) at org.apache.trevni.avro.mapreduce.TestKeyValueWordCount.testIOFormat(TestKeyValueWordCount.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at org.junit.runners.ParentRunner.run(ParentRunner.java:300) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
Re: [VOTE] Avro release 1.7.5 (rc0)
On Tue, Aug 20, 2013 at 6:31 AM, Rodrigo Trujillo rodrigo.truji...@linux.vnet.ibm.com wrote: any chance to add this patch to 1.7.5 release ? Or next ? https://issues.apache.org/jira/browse/AVRO-1336 It's too late for 1.7.5. But we can include it in the next release. Sorry! It was marked for 1.7.4, so I didn't see it when looking for issues for 1.7.5. The Fix Version should be set to the release that we expect to include a fix in. We cannot change what's in a release that's already out. We can only make new releases. We may next make a 1.7.6 release with compatible changes from 1.7.5, or, if we need to include some incompatible changes, the next release will be called 1.8.0. Or we might make both, if folks need. Doug
[jira] [Commented] (AVRO-975) Support RPC in C#
[ https://issues.apache.org/jira/browse/AVRO-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745292#comment-13745292 ] ASF subversion and git services commented on AVRO-975: -- Commit 1515933 from [~cutting] in branch 'avro/trunk' [ https://svn.apache.org/r1515933 ] AVRO-975. C#: Add RPC support. Contributed by Mark Lamley. Support RPC in C# - Key: AVRO-975 URL: https://issues.apache.org/jira/browse/AVRO-975 Project: Avro Issue Type: New Feature Components: csharp Affects Versions: 1.6.1 Reporter: Jeff Hammerbacher Attachments: 975.patch, Avro-975-00.patch, Avro-975-complate5.patch, Avro-975-complete2.patch, Avro-975-complete3.patch, Avro-975-complete4.patch, Avro975-complete.patch, buildtask.patch, Castle.Core.dll, errors-and-remote-protocols.975.diff, java-compat.diff, propagate-exception.diff, timeout-unhandled-exception.diff, types_ipc.diff, types_main.diff -- 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-975) Support RPC in C#
[ https://issues.apache.org/jira/browse/AVRO-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated AVRO-975: -- Resolution: Fixed Fix Version/s: 1.7.6 Assignee: Mark Lamley Status: Resolved (was: Patch Available) I committed this. Thanks, Mark! Support RPC in C# - Key: AVRO-975 URL: https://issues.apache.org/jira/browse/AVRO-975 Project: Avro Issue Type: New Feature Components: csharp Affects Versions: 1.6.1 Reporter: Jeff Hammerbacher Assignee: Mark Lamley Fix For: 1.7.6 Attachments: 975.patch, Avro-975-00.patch, Avro-975-complate5.patch, Avro-975-complete2.patch, Avro-975-complete3.patch, Avro-975-complete4.patch, Avro975-complete.patch, buildtask.patch, Castle.Core.dll, errors-and-remote-protocols.975.diff, java-compat.diff, propagate-exception.diff, timeout-unhandled-exception.diff, types_ipc.diff, types_main.diff -- 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-975) Support RPC in C#
[ https://issues.apache.org/jira/browse/AVRO-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745313#comment-13745313 ] Hudson commented on AVRO-975: - SUCCESS: Integrated in AvroJava #392 (See [https://builds.apache.org/job/AvroJava/392/]) AVRO-975. C#: Add RPC support. Contributed by Mark Lamley. (cutting: rev 1515933) * /avro/trunk/CHANGES.txt * /avro/trunk/lang/csharp * /avro/trunk/lang/csharp/.gitignore * /avro/trunk/lang/csharp/Avro.nunit * /avro/trunk/lang/csharp/Avro.sln * /avro/trunk/lang/csharp/lib/main/Castle.Core.dll * /avro/trunk/lang/csharp/src/apache/codegen/AvroGen.cs * /avro/trunk/lang/csharp/src/apache/codegen/Properties/AssemblyInfo.cs * /avro/trunk/lang/csharp/src/apache/ipc * /avro/trunk/lang/csharp/src/apache/ipc/Avro.ipc.csproj * /avro/trunk/lang/csharp/src/apache/ipc/CallFuture.cs * /avro/trunk/lang/csharp/src/apache/ipc/CountdownLatch.cs * /avro/trunk/lang/csharp/src/apache/ipc/Generic * /avro/trunk/lang/csharp/src/apache/ipc/Generic/GenericRequestor.cs * /avro/trunk/lang/csharp/src/apache/ipc/Generic/GenericResponder.cs * /avro/trunk/lang/csharp/src/apache/ipc/LocalTransceiver.cs * /avro/trunk/lang/csharp/src/apache/ipc/OutputStream.cs * /avro/trunk/lang/csharp/src/apache/ipc/Properties * /avro/trunk/lang/csharp/src/apache/ipc/Properties/AssemblyInfo.cs * /avro/trunk/lang/csharp/src/apache/ipc/Requestor.cs * /avro/trunk/lang/csharp/src/apache/ipc/Responder.cs * /avro/trunk/lang/csharp/src/apache/ipc/RpcContext.cs * /avro/trunk/lang/csharp/src/apache/ipc/RpcRequest.cs * /avro/trunk/lang/csharp/src/apache/ipc/SocketServer.cs * /avro/trunk/lang/csharp/src/apache/ipc/SocketTransceiver.cs * /avro/trunk/lang/csharp/src/apache/ipc/Specific * /avro/trunk/lang/csharp/src/apache/ipc/Specific/SpecificRequestor.cs * /avro/trunk/lang/csharp/src/apache/ipc/Specific/SpecificResponder.cs * /avro/trunk/lang/csharp/src/apache/ipc/Transceiver.cs * /avro/trunk/lang/csharp/src/apache/ipc/org * /avro/trunk/lang/csharp/src/apache/ipc/org/apache * /avro/trunk/lang/csharp/src/apache/ipc/org/apache/avro * /avro/trunk/lang/csharp/src/apache/ipc/org/apache/avro/ipc * /avro/trunk/lang/csharp/src/apache/ipc/org/apache/avro/ipc/HandshakeMatch.cs * /avro/trunk/lang/csharp/src/apache/ipc/org/apache/avro/ipc/HandshakeRequest.cs * /avro/trunk/lang/csharp/src/apache/ipc/org/apache/avro/ipc/HandshakeResponse.cs * /avro/trunk/lang/csharp/src/apache/ipc/org/apache/avro/ipc/MD5.cs * /avro/trunk/lang/csharp/src/apache/main/Avro.main.csproj * /avro/trunk/lang/csharp/src/apache/main/CodeGen/CodeGen.cs * /avro/trunk/lang/csharp/src/apache/main/File/DataFileReader.cs * /avro/trunk/lang/csharp/src/apache/main/Generic/GenericReader.cs * /avro/trunk/lang/csharp/src/apache/main/Generic/GenericWriter.cs * /avro/trunk/lang/csharp/src/apache/main/IO/BinaryEncoder.cs * /avro/trunk/lang/csharp/src/apache/main/IO/ByteBufferInputStream.cs * /avro/trunk/lang/csharp/src/apache/main/IO/ByteBufferOutputStream.cs * /avro/trunk/lang/csharp/src/apache/main/IO/ICallback.cs * /avro/trunk/lang/csharp/src/apache/main/IO/InputStream.cs * /avro/trunk/lang/csharp/src/apache/main/IO/OutputStream.cs * /avro/trunk/lang/csharp/src/apache/main/Properties/AssemblyInfo.cs * /avro/trunk/lang/csharp/src/apache/main/Protocol/Message.cs * /avro/trunk/lang/csharp/src/apache/main/Schema/MapSchema.cs * /avro/trunk/lang/csharp/src/apache/main/Schema/RecordSchema.cs * /avro/trunk/lang/csharp/src/apache/main/Specific/ObjectCreator.cs * /avro/trunk/lang/csharp/src/apache/main/Specific/SpecificException.cs * /avro/trunk/lang/csharp/src/apache/main/Specific/SpecificFixed.cs * /avro/trunk/lang/csharp/src/apache/main/Specific/SpecificProtocol.cs * /avro/trunk/lang/csharp/src/apache/main/Specific/SpecificReader.cs * /avro/trunk/lang/csharp/src/apache/main/Specific/SpecificWriter.cs * /avro/trunk/lang/csharp/src/apache/msbuild * /avro/trunk/lang/csharp/src/apache/msbuild/Avro.msbuild.csproj * /avro/trunk/lang/csharp/src/apache/msbuild/AvroBuilldTask.cs * /avro/trunk/lang/csharp/src/apache/msbuild/Properties * /avro/trunk/lang/csharp/src/apache/msbuild/Properties/AssemblyInfo.cs * /avro/trunk/lang/csharp/src/apache/test/Avro.test.csproj * /avro/trunk/lang/csharp/src/apache/test/CodGen/CodeGenTest.cs * /avro/trunk/lang/csharp/src/apache/test/Ipc * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org/apache * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org/apache/avro * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org/apache/avro/test * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org/apache/avro/test/All.cs * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org/apache/avro/test/AllCallback.cs * /avro/trunk/lang/csharp/src/apache/test/Ipc/GeneratedFiles/org/apache/avro/test/AllEnum.cs *
[jira] [Updated] (AVRO-1355) Record schema should reject duplicate field names
[ https://issues.apache.org/jira/browse/AVRO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Cutting updated AVRO-1355: --- Resolution: Fixed Fix Version/s: 1.7.6 Status: Resolved (was: Patch Available) I committed this. Thanks, Christophe! Record schema should reject duplicate field names - Key: AVRO-1355 URL: https://issues.apache.org/jira/browse/AVRO-1355 Project: Avro Issue Type: Bug Components: java Affects Versions: 1.7.4 Reporter: Christophe Taton Assignee: Christophe Taton Fix For: 1.7.6 Attachments: AVRO-1355.diff Schema.createRecord() should not accept a field list that includes fields with duplicate names. -- 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-1355) Record schema should reject duplicate field names
[ https://issues.apache.org/jira/browse/AVRO-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13745356#comment-13745356 ] ASF subversion and git services commented on AVRO-1355: --- Commit 1515957 from [~cutting] in branch 'avro/trunk' [ https://svn.apache.org/r1515957 ] AVRO-1355. Java: Reject schemas with duplicate field names. Contributed by Christophe Taton. Record schema should reject duplicate field names - Key: AVRO-1355 URL: https://issues.apache.org/jira/browse/AVRO-1355 Project: Avro Issue Type: Bug Components: java Affects Versions: 1.7.4 Reporter: Christophe Taton Assignee: Christophe Taton Attachments: AVRO-1355.diff Schema.createRecord() should not accept a field list that includes fields with duplicate names. -- 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
