[
https://issues.apache.org/jira/browse/AVRO-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482324#comment-14482324
]
Ryan Blue commented on AVRO-1660:
---------------------------------
If I'm reading this patch correctly, it throws an exception if there would be a
name collision on case insensitive file systems. I don't think that's the
correct behavior because it should work for case sensitive file systems. I
think the right thing to do would be to detect the case where the file already
exists and fail, which would be consistent because files would never be
accidentally overwritten.
But the current overwrite behavior is the current expectation and I think it's
more likely that it is a part of workflows using the tool -- to overwrite the
result of previous runs -- than it is that people have schema name collisions
from case insensitivity. So I think the right thing to do is to not make these
changes. Does that sound reasonable?
> case sensitivity affects schema to java file generation
> -------------------------------------------------------
>
> Key: AVRO-1660
> URL: https://issues.apache.org/jira/browse/AVRO-1660
> Project: Avro
> Issue Type: Bug
> Affects Versions: 1.7.7
> Environment: mac OS X
> Reporter: Balaji Ambresh
> Fix For: 1.7.7
>
> Attachments: delta.diff
>
>
> On a linux box, creating 2 schemas with com.example.organization and
> com.example.Organization will compile fine. 2 files (organization.java and
> Organization.java) would get generated. On a mac however, both files would be
> treated the same. This could be caught while generating the file(s).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
