[ 
https://issues.apache.org/jira/browse/AVRO-3622?focusedWorklogId=805131&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-805131
 ]

ASF GitHub Bot logged work on AVRO-3622:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Aug/22 08:08
            Start Date: 31/Aug/22 08:08
    Worklog Time Spent: 10m 
      Work Description: jjaakola-aiven commented on PR #1843:
URL: https://github.com/apache/avro/pull/1843#issuecomment-1232606778

   @martin-g I don't have enough insight if the Rust impl is correct. Like 
@perj notes the null namespace is not valid for dot separated names per 
specification. I think this is up for Avro maintainers to decide if `.record` 
is a valid or invalid name.
   
   Java accepts this `new Schema.Name(".record", null);` Seems Rust accepts 
also. Python does not. Please note that I did not change the validation 
functionality of the name in this PR, I added a test for case `.record`. I just 
tested with Python lib version `1.11.0` and it raises also 
`avro.errors.InvalidName`. So this behavior was already in Python lib.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 805131)
    Time Spent: 1.5h  (was: 1h 20m)

> Python compatibility check fails if record with and without namespace are 
> compared
> ----------------------------------------------------------------------------------
>
>                 Key: AVRO-3622
>                 URL: https://issues.apache.org/jira/browse/AVRO-3622
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: python
>    Affects Versions: 1.11.1
>            Reporter: Jarkko Jaakola
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Avro spec:
> {noformat}
>  To match, one of the following must hold:
> ...
>   * both schemas are records with the same (unqualified) name{noformat}
> Following records are compatible. The `ReaderWriterCompatibilityChecker` 
> reports name mismatch and an incompatibility. Similar test case with Java 
> implementation passes.
> {code:java}
> WITHOUT_NAMESPACE_RECORD = parse(
>     json.dumps(
>         {
>             "type": SchemaType.RECORD,
>             "name": "Record1",
>             "fields": [
>                 {
>                     "name": "f1",
>                     "type": "int",
>                 }
>             ],
>         },
>     )
> )
> WITH_NAMESPACE_RECORD = parse(
>     json.dumps(
>         {
>             "type": SchemaType.RECORD,
>             "name": "ns.Record1",
>             "fields": [
>                 {
>                     "name": "f1",
>                     "type": "int",
>                 }
>             ],
>         },
>     )
> )
>  
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to