[
https://issues.apache.org/jira/browse/ATLAS-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921890#comment-16921890
]
Madhan Neethiraj commented on ATLAS-3393:
-----------------------------------------
[~bolke] - as I mentioned earlier, changing name of
attribute/entity-def/struct-def/enum-def/enum-element will likely to break any
application that use the earlier name. It isn't difficult to see the impact of
such rename: consider renaming the other way i.e. 'createTime' -> 'createtime';
this attribute is referenced in following entity-defs; this rename would break
existing integrations including Hive Hook, HBase hook, Spark hook and other
applications that deal with these types.
{noformat}
aws_s3_object
aws_s3_pseudo_dir
fs_path
hbase_column_family
hbase_namespace
hbase_table
hive_table
spark_table
rdbms_table
{noformat}
Hence I suggest to not take up this attribute rename.
bq. we encountered this bug due to integration issues with our tooling
expecting "createTime" as it is used everywhere else
If the tooling referenced above deals with all entity-defs (existing and future
defs), consider an option to look for multiple attribute names for the concept
of 'createTime'.
> Fix inconsistency with attribute createtime in aws_s3_bucket
> ------------------------------------------------------------
>
> Key: ATLAS-3393
> URL: https://issues.apache.org/jira/browse/ATLAS-3393
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 1.2.0, 2.0.0
> Reporter: Bolke de Bruin
> Priority: Critical
>
> attributes are in camelcase. in aws_s3_bukcket createtime isnt
>
> (fix available in linked issue/pr)
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
