[jira] [Assigned] (ATLAS-369) Publish 0.6-incubating artifacts
[ https://issues.apache.org/jira/browse/ATLAS-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad reassigned ATLAS-369: -- Assignee: Suma Shivaprasad > Publish 0.6-incubating artifacts > > > Key: ATLAS-369 > URL: https://issues.apache.org/jira/browse/ATLAS-369 > Project: Atlas > Issue Type: Sub-task >Reporter: Shwetha G S >Assignee: Suma Shivaprasad > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-375) Improve the way we manage the display of 'Schema' information in the entity details view
Hemanth Yamijala created ATLAS-375: -- Summary: Improve the way we manage the display of 'Schema' information in the entity details view Key: ATLAS-375 URL: https://issues.apache.org/jira/browse/ATLAS-375 Project: Atlas Issue Type: Improvement Reporter: Hemanth Yamijala Currently, we show a 'Schema' tab for hive_table which lists all the columns. This JIRA proposes some improvements that need to be done for the same. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
Hemanth Yamijala created ATLAS-376: -- Summary: UI: Use the Schema API of the backend to populate details for Schema tab Key: ATLAS-376 URL: https://issues.apache.org/jira/browse/ATLAS-376 Project: Atlas Issue Type: Task Reporter: Hemanth Yamijala Currently, the information that comes in the schema tab seems to be populated from the entity information that is fired to get the details of the entity. In the API, we have a specific API to get schema of any dataset. This API should be used to populate the schema tab instead of using information from the entity information. Specifically: * Use the entity API, something of the form /lineage/hive/table/$name$/schema where $name$ is the name attribute of the entity in question. For e.g. for hive_tables an example URL would be /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where default.tbl16@primary is the name. * The results of the API should be parsed to populate the details of the Schema table. (Will attach a sample response, and expand more details on this point in the comments). * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. Hive columns), it should put up the 'Add tag' action and should allow the user to associate a tag to that entity. In addition, it should put up the list of available tags currently associated with the entity. (Note this functionality is similar to how the search results are handled for reference-able entities) * The API could return a 404 if the name does not exist, or the name is something that does not represent a dataset. This should be handled, and upon receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-376: --- Attachment: schema_response.json Attaching the sample response for the schema API. > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala > Attachments: schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-377) API: Return all super types of an entity
Hemanth Yamijala created ATLAS-377: -- Summary: API: Return all super types of an entity Key: ATLAS-377 URL: https://issues.apache.org/jira/browse/ATLAS-377 Project: Atlas Issue Type: Sub-task Reporter: Hemanth Yamijala Currently, Atlas type API returns only the immediate super-type of a type. In some scenarios, it would be beneficial to also know if this type is a descendant of some type. For e.g. the Schema API only makes sense for entities of type DataSet. Given this, a UI can check if a type of an entity is descending from a DataSet and based on that choose to make or suppress the schema API call. To support this, all super types of a type should be returned in the result of the type API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-376: --- Issue Type: Sub-task (was: Task) Parent: ATLAS-375 > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-378) UI: Suppress the call to Schema API if entity is not a DataSet.
Hemanth Yamijala created ATLAS-378: -- Summary: UI: Suppress the call to Schema API if entity is not a DataSet. Key: ATLAS-378 URL: https://issues.apache.org/jira/browse/ATLAS-378 Project: Atlas Issue Type: Sub-task Reporter: Hemanth Yamijala As described in ATLAS-377, the UI should make the Schema API call only when its super type is a DataSet. This way, it could avoid making an unnecessary API call that is bound to return a 404. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar reassigned ATLAS-376: --- Assignee: Darshan Kumar > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Attachments: schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Release Apache Atlas version 0.6-incubating
Hi Folks, I have created a build for Apache Atlas 0.6-incubating, release candidate 0. Thanks to everyone who have contributed to this release and also tested this. The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha): > https://dist.apache.org/repos/dist/dev/incubator/atlas/0.6.0-incubating-rc0 The SHA512 checksum of the archive is 1D86B6B3 C89DAC70 31ACAB27 3D77F0AD 078A6080 694F9B66 668029A1 8289ECCC 48FE013F 84069800 768D9C11 2B4119DA 85BB210D A02188D1 A09BE223 399A92DF The commit id (adb6c76db6c262fd538cb81be2e0538ab24ae4ce) to be voted upon: > https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=adb6c76db6c262fd538cb81be2e0538ab24ae4ce The tag to be voted upon: > https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=tag;h=refs/tags/release-0.6-rc0 The list of fixed issues: > https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;h=1dae6fb46376cbd0369784d9d4e2a29c99dec025;hb=51656991fc008e57936bfc12afa51b9e372ae6a5 Keys to verify the signature of the release artifact are available at: http://www.apache.org/dist/incubator/atlas/KEYS PGP release keys: http://pgp.mit.edu/pks/lookup?op=vindex=0x2DBD4D9B Note that this is a source only release and we are voting on the source (release-0.6-incubating-rc0 / Commit: adb6c76db6c262fd538cb81be2e0538ab24ae4ce / SHA512: 1D86B6B3 C89DAC70 31ACAB27 3D77F0AD 078A6080 694F9B66 668029A1 8289ECCC 48FE013F 84069800 768D9C11 2B4119DA 85BB210D A02188D1 A09BE223 399A92DF). Please download, test, and try it out. Vote will be open for at least 72 hours - (6:30 AM PST/ 8 PM IST/ 9:30 AM IST) (until the required number of IPMC votes are obtained). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) +1 from my side for the release. For folks not familiar with vetting a release, please refer to http://incubator.apache.org/guides/releasemanagement.html#check-list Regards, Suma
[jira] [Commented] (ATLAS-314) UI: use schema API exclusively instead of schema from details API.
[ https://issues.apache.org/jira/browse/ATLAS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047366#comment-15047366 ] Darshan Kumar commented on ATLAS-314: - This is a part of ATLAS-376 > UI: use schema API exclusively instead of schema from details API. > -- > > Key: ATLAS-314 > URL: https://issues.apache.org/jira/browse/ATLAS-314 > Project: Atlas > Issue Type: Task >Reporter: roshni gadiyar >Assignee: Darshan Kumar >Priority: Minor > Labels: Atlas-UI > > use schema API exclusively instead of schema from details api. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-380) Fix ATLAS source artifact generation
[ https://issues.apache.org/jira/browse/ATLAS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15048227#comment-15048227 ] Shwetha G S commented on ATLAS-380: --- +1 > Fix ATLAS source artifact generation > > > Key: ATLAS-380 > URL: https://issues.apache.org/jira/browse/ATLAS-380 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > Attachments: ATLAS-380.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-380) Fix ATLAS source artifact generation
[ https://issues.apache.org/jira/browse/ATLAS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-380: --- Attachment: ATLAS-380.1.patch > Fix ATLAS source artifact generation > > > Key: ATLAS-380 > URL: https://issues.apache.org/jira/browse/ATLAS-380 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > Attachments: ATLAS-380.1.patch, ATLAS-380.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-380) Fix ATLAS source artifact generation
[ https://issues.apache.org/jira/browse/ATLAS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-380: --- Attachment: ATLAS-380.patch > Fix ATLAS source artifact generation > > > Key: ATLAS-380 > URL: https://issues.apache.org/jira/browse/ATLAS-380 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > Attachments: ATLAS-380.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047526#comment-15047526 ] David Kantor commented on ATLAS-106: [~suma.shivaprasad] Thanks for pointing out the recent commit of ATLAS-47. I have reapplied my changes against the latest source and generated a new patch. Please review and let me know if there are any further issues. > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > Attachments: ATLAS-106-v1.patch > > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-185) Add data model for Sqoop process
[ https://issues.apache.org/jira/browse/ATLAS-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-185. --- Resolution: Duplicate ATLAS-379 > Add data model for Sqoop process > > > Key: ATLAS-185 > URL: https://issues.apache.org/jira/browse/ATLAS-185 > Project: Atlas > Issue Type: Sub-task >Affects Versions: 0.6-incubating >Reporter: Venkatesh Seetharam > Fix For: 0.6-incubating > > > This could be modeled after Hive data model. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-380) Fix ATLAS source artifact generation
[ https://issues.apache.org/jira/browse/ATLAS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-380: --- Affects Version/s: 0.6-incubating > Fix ATLAS source artifact generation > > > Key: ATLAS-380 > URL: https://issues.apache.org/jira/browse/ATLAS-380 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ATLAS-380) Fix ATLAS source artifact generation
Suma Shivaprasad created ATLAS-380: -- Summary: Fix ATLAS source artifact generation Key: ATLAS-380 URL: https://issues.apache.org/jira/browse/ATLAS-380 Project: Atlas Issue Type: Bug Reporter: Suma Shivaprasad Assignee: Suma Shivaprasad -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-184) Integrate Sqoop metadata into Atlas
[ https://issues.apache.org/jira/browse/ATLAS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-184. --- Resolution: Duplicate ATLAS-379 > Integrate Sqoop metadata into Atlas > --- > > Key: ATLAS-184 > URL: https://issues.apache.org/jira/browse/ATLAS-184 > Project: Atlas > Issue Type: Improvement >Affects Versions: 0.6-incubating >Reporter: Venkatesh Seetharam > Fix For: 0.6-incubating > > > Apache Sqoop Integration with Apache Atlas (incubating) > Introduction > Apache Sqoop is a tool designed for efficiently transferring bulk data > between Apache Hadoop and structured data stores such as relational databases. > Apache Atlas is a metadata repository that enables end-to-end data lineage, > search and associate business classification. > Overview > The goal of this integration is to at minimum push the Sqoop generated query > metadata along with the source provenance, target(s), and any available > business context so Atlas can capture the lineage for this topology. > There are 2 parts in this process detailed below: > 1.Data model to represent the concepts in Sqoop > 2.Sqoop Bridge/Hook to update metadata in Atlas > Data Model > A data model is represented as a Type in Atlas. This can reuse or closely be > modeled after Hive data types that already exist. At the least, we need to > create types for: > • Sqoop processes containing the SQL query text, start/end times, user, > etc. > • Source Provenance, fine-grained at DB, Table, Column, etc. so we have a > 1-1 mapping between source and target assets > • Target (typically Hive, HBase, HDFS, etc.) > You can take a look at the data model code for Hive. Sqoop should reuse the > data model from Hive or closely model after that. > Pushing Metadata into Atlas > There are 2 parts to the bridge: > 1.Sqoop Bridge > This does not apply to Sqoop tool. However, will apply if and when we migrate > to Sqoop 2. > 2.Post-execution Hook > Atlas needs to be notified when a new Sqoop Ingest is executed successfully > or when someone changes the definition of an existing Sqoop Job. > You can refer to the hook code for Hive. > 3.Column-level lineage > It would be good to have column level lineage for data flowing from the > source database/WH into Hive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-69) Add Falcon Bridge and Hook for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S resolved ATLAS-69. -- Resolution: Duplicate ATLAS-379 > Add Falcon Bridge and Hook for Atlas > > > Key: ATLAS-69 > URL: https://issues.apache.org/jira/browse/ATLAS-69 > Project: Atlas > Issue Type: New Feature >Reporter: Suma Shivaprasad > > Add a falcon plugin to consume falcon entities like cluster, feed, process > into ATLAS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab
[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darshan Kumar updated ATLAS-376: Attachment: ATLAS-376-ATLAS-314.patch > UI: Use the Schema API of the backend to populate details for Schema tab > > > Key: ATLAS-376 > URL: https://issues.apache.org/jira/browse/ATLAS-376 > Project: Atlas > Issue Type: Sub-task >Reporter: Hemanth Yamijala >Assignee: Darshan Kumar > Attachments: ATLAS-376-ATLAS-314.patch, schema_response.json > > > Currently, the information that comes in the schema tab seems to be populated > from the entity information that is fired to get the details of the entity. > In the API, we have a specific API to get schema of any dataset. This API > should be used to populate the schema tab instead of using information from > the entity information. > Specifically: > * Use the entity API, something of the form /lineage/hive/table/$name$/schema > where $name$ is the name attribute of the entity in question. For e.g. for > hive_tables an example URL would be > /api/atlas/lineage/hive/table/default.tbl16@primary/schema, where > default.tbl16@primary is the name. > * The results of the API should be parsed to populate the details of the > Schema table. (Will attach a sample response, and expand more details on this > point in the comments). > * If the results contains a referenceable entity, i.e. has an $id$, (for e.g. > Hive columns), it should put up the 'Add tag' action and should allow the > user to associate a tag to that entity. In addition, it should put up the > list of available tags currently associated with the entity. (Note this > functionality is similar to how the search results are handled for > reference-able entities) > * The API could return a 404 if the name does not exist, or the name is > something that does not represent a dataset. This should be handled, and upon > receipt should not display the Schema tab at all. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-380) Fix ATLAS source artifact generation
[ https://issues.apache.org/jira/browse/ATLAS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15048136#comment-15048136 ] Suma Shivaprasad commented on ATLAS-380: The distro module currently generates source articfact which includes the current modules src files and should generate an artifact having the entire ATLAS source code > Fix ATLAS source artifact generation > > > Key: ATLAS-380 > URL: https://issues.apache.org/jira/browse/ATLAS-380 > Project: Atlas > Issue Type: Bug >Affects Versions: 0.6-incubating >Reporter: Suma Shivaprasad >Assignee: Suma Shivaprasad > Fix For: 0.6-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kantor updated ATLAS-106: --- Attachment: (was: ATLAS-106-v0.patch) > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > Attachments: ATLAS-106-v1.patch > > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-106) Store createTimestamp and modified timestamp separately for an entity
[ https://issues.apache.org/jira/browse/ATLAS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kantor updated ATLAS-106: --- Attachment: ATLAS-106-v1.patch > Store createTimestamp and modified timestamp separately for an entity > - > > Key: ATLAS-106 > URL: https://issues.apache.org/jira/browse/ATLAS-106 > Project: Atlas > Issue Type: Improvement >Reporter: Suma Shivaprasad >Assignee: David Kantor > Attachments: ATLAS-106-v1.patch > > > Currently we store only the Create timestamp in atlas. Would be better to > separate to track create and modified time separately , in cases where we > want to support search queries give all entities which have been modified in > the past 1 day etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
