Repository: incubator-atlas Updated Branches: refs/heads/master 4bd2df49e -> 646f29c37
ATLAS-421 typo in Architecture.twiki (dbist13 via shwethags) Project: http://git-wip-us.apache.org/repos/asf/incubator-atlas/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/646f29c3 Tree: http://git-wip-us.apache.org/repos/asf/incubator-atlas/tree/646f29c3 Diff: http://git-wip-us.apache.org/repos/asf/incubator-atlas/diff/646f29c3 Branch: refs/heads/master Commit: 646f29c37deb394cdcce71a3c7499e19367eba0c Parents: 4bd2df4 Author: Shwetha GS <[email protected]> Authored: Thu Jan 7 12:29:56 2016 +0530 Committer: Shwetha GS <[email protected]> Committed: Thu Jan 7 12:29:56 2016 +0530 ---------------------------------------------------------------------- docs/src/site/twiki/Architecture.twiki | 2 +- release-log.txt | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-atlas/blob/646f29c3/docs/src/site/twiki/Architecture.twiki ---------------------------------------------------------------------- diff --git a/docs/src/site/twiki/Architecture.twiki b/docs/src/site/twiki/Architecture.twiki index 8966cbe..7bfe4b6 100755 --- a/docs/src/site/twiki/Architecture.twiki +++ b/docs/src/site/twiki/Architecture.twiki @@ -17,7 +17,7 @@ Architecturally, Atlas has the following components: ---++ Bridges External components like hive/sqoop/storm/falcon should model their taxonomy using typesystem and register the types with Atlas. For every entity created in this external component, the corresponding entity should be registered in Atlas as well. This is typically done in a hook which runs in the external component and is called for every entity operation. Hook generally processes the entity asynchronously using a thread pool to avoid adding latency to the main operation. -The hook can then build the entity and register the entity using Atlas REST APIs. Howerver, any failure in APIs because of network issue etc can in result entity not registered in Atlas and hence inconsistent metadata. +The hook can then build the entity and register the entity using Atlas REST APIs. Howerver, any failure in APIs because of network issue etc can result in entity not registered in Atlas and hence inconsistent metadata. Atlas exposes notification interface and can be used for reliable entity registration by hook as well. The hook can send notification message containing the list of entities to be registered. Atlas service contains hook consumer that listens to these messages and registers the entities. http://git-wip-us.apache.org/repos/asf/incubator-atlas/blob/646f29c3/release-log.txt ---------------------------------------------------------------------- diff --git a/release-log.txt b/release-log.txt index d46627c..ba81539 100644 --- a/release-log.txt +++ b/release-log.txt @@ -6,6 +6,7 @@ INCOMPATIBLE CHANGES: ATLAS-379 Create sqoop and falcon metadata addons (venkatnrangan,bvellanki,sowmyaramesh via shwethags) ALL CHANGES: +ATLAS-421 typo in Architecture.twiki (dbist13 via shwethags) ATLAS-387 Running quick_start without a valid atlas endpoint in configuration or argument prints a spurious success message (yhemanth via shwethags) ATLAS-182 Add data model for Storm topology elements (svenkat,yhemanth via shwethags) ATLAS-414 Doc: Increase MAVEN_OPTS limit to 512m in InstallationSteps.twiki (yhemanth via shwethags)
