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

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

Commit 4f2b0150b86242048b74b49fb3df4ebd30b2058c in avro's branch 
refs/heads/dependabot/cargo/lang/rust/master/serde-1.0.183 from Rémi Piotaix
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=4f2b0150b ]

AVRO-3790: [Ruby] Provide namespace on UnknownSchemaError raise (#2409)



> [RUBY] Missing default namespace information in SchemaParseError
> ----------------------------------------------------------------
>
>                 Key: AVRO-3790
>                 URL: https://issues.apache.org/jira/browse/AVRO-3790
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: ruby
>    Affects Versions: 1.11.1
>            Reporter: Rémi Piotaix
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 1.12.0, 1.11.3
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The Avro::SchemaParseError exception only has information about the type name 
> that is missing.
> However, when nesting schemas (record fields):
> - [If] A name only is specified, i.e., a name that contains no dots. In this 
> case the namespace is taken from the most tightly enclosing schema or 
> protocol. For example, if "name": "X" is specified, and this occurs within a 
> field of the record definition of org.foo.Y, then the fullname is org.foo.X. 
> If there is no enclosing namespace then the null namespace is used.
>  
> The UnknownSchemaError is raised in Avro::Schema.real_parse that already has 
> the `default_namespace` parameter. It should be just a matter of adding this 
> attribute to the error class.



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

Reply via email to