[jira] [Commented] (AVRO-2322) Compatibility checks report false positive when record fullnames differ

[Doug Cutting (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779745#comment-16779745
 ] 

Doug Cutting commented on AVRO-2322:


AVRO-1590 seems like an instance of Postel's law (liberal in what's accepted, 
strict in what's produced).  When a union contains no perfect match but does 
contains a match that is structurally identical but differently named, that is 
accepted by the Java implementation.  I think this was for back-compatibility: 
record names have not always been validated consistently on read.  But written 
data should never mismatch its schema.

Validation, if used to check for cross-language compatibility, should arguably 
not be so liberal.  That said, there may be applications that depend on this.  
Does that help?

> Compatibility checks report false positive when record fullnames differ
> ---
>
> Key: AVRO-2322
> URL: https://issues.apache.org/jira/browse/AVRO-2322
> Project: Apache Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.8.1, 1.8.2
>Reporter: Chris Egerton
>Priority: Major
>
> When testing for backward compatibility between two record schemas which 
> differ in their fullnames (namespace + name) but are otherwise identical, a 
> false positive is reported.
> Example:
> {code:java}
> // Create two schemas with differing fullnames and no fields
> Schema writtenSchema = Schema.createRecord("write", null, "namespace", false, 
> Collections.emptyList());
> Schema readSchema = Schema.createRecord("read", null, "namespace", false, 
> Collections.emptyList());
> // Validate the two schemas for compatibility
> // Should throw a SchemaValidationException; does not
> new 
> SchemaValidatorBuilder().canReadStrategy().validateLatest().validate(readSchema,
>  Collections.singleton(writtenSchema));{code}
> It looks like this behavior partially stems from discussion on AVRO-1590, 
> although I'm unfortunately not familiar enough with some of the concepts 
> brought up there to understand why it's advantageous to deviate from the spec 
> like this.
> I'd be happy to work on a fix myself; just want to understand how to 
> implement this correctly without stepping on the decisions of others before 
> opening a PR.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Jenkins build is back to normal : AvroJava #608

[Apache Jenkins Server]

See 

[jira] [Commented] (AVRO-2325) Bump commons-codec from 1.11 to 1.12

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779208#comment-16779208
 ] 

ASF subversion and git services commented on AVRO-2325:
---

Commit b82a370b1607d6f45c3ec9db6125dd527d5eaab5 in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=b82a370 ]

[AVRO-2325] Bump commons-codec from 1.11 to 1.12 (#457)



> Bump commons-codec from 1.11 to 1.12
> 
>
> Key: AVRO-2325
> URL: https://issues.apache.org/jira/browse/AVRO-2325
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.2
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AVRO-2325) Bump commons-codec from 1.11 to 1.12

[Fokko Driesprong (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fokko Driesprong resolved AVRO-2325.

Resolution: Fixed

> Bump commons-codec from 1.11 to 1.12
> 
>
> Key: AVRO-2325
> URL: https://issues.apache.org/jira/browse/AVRO-2325
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.2
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (AVRO-2326) Bump netty-codec-http2 from 4.1.30.Final to 4.1.33.Final

[Fokko Driesprong (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fokko Driesprong resolved AVRO-2326.

Resolution: Fixed

> Bump netty-codec-http2 from 4.1.30.Final to 4.1.33.Final
> 
>
> Key: AVRO-2326
> URL: https://issues.apache.org/jira/browse/AVRO-2326
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.2
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AVRO-2326) Bump netty-codec-http2 from 4.1.30.Final to 4.1.33.Final

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779185#comment-16779185
 ] 

ASF subversion and git services commented on AVRO-2326:
---

Commit e2ca27ef053becb47d3b18a00215e9df3da3ad2a in avro's branch 
refs/heads/master from Fokko Driesprong
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=e2ca27e ]

[AVRO-2326] Bump commons-codec from 1.11 to 1.12 (#458)



> Bump netty-codec-http2 from 4.1.30.Final to 4.1.33.Final
> 
>
> Key: AVRO-2326
> URL: https://issues.apache.org/jira/browse/AVRO-2326
> Project: Apache Avro
>  Issue Type: Improvement
>  Components: java
>Affects Versions: 1.8.2
>Reporter: Fokko Driesprong
>Assignee: Fokko Driesprong
>Priority: Major
> Fix For: 1.9.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)