BES: Root Catalog - Revision history

Ndp: /* Discussion */

2012-04-12T16:47:52Z

Discussion

← Older revision		Revision as of 16:47, 12 April 2012
Line 38:		Line 38:

	[[User:Ndp\|ndp]] 19:03, 11 April 2012 (PDT)		[[User:Ndp\|ndp]] 19:03, 11 April 2012 (PDT)
	* It seems like it might be pretty cool to allow the ~~root~~ catalog to use any of the catalogs as "root" and map the others into the top level of that. Or maybe even map the others into not just the top level (maybe that's a default) but to any path specified in a configuration of the root catalog...		* It seems like it might be pretty cool to allow the meta catalog to use any of the catalogs as "root" and map the others into the top level of that. Or maybe even map the others into not just the top level (maybe that's a default) but to any path specified in a configuration of the root catalog...
	* We might consider making the root catalog be configurable to build the root node as a collection of the root nodes of it's catalogs. Or it could be configured to use any one of it's catalogs as a root catalog and then map the others into it's root node.		* We might consider making the root catalog be configurable to build the root node as a collection of the root nodes of it's catalogs. Or it could be configured to use any one of it's catalogs as a root catalog and then map the others into it's root node.

Ndp: /* Proposed solution */

2012-04-12T16:46:41Z

Proposed solution

← Older revision		Revision as of 16:46, 12 April 2012
Line 25:		Line 25:
	# If the child catalog name conflicts with one of the file system holdings then the catalog should take precedence, and the BES should write an <del>error</del>([[User:Jimg\|Jimg]]) warning message regarding this to it's logs.		# If the child catalog name conflicts with one of the file system holdings then the catalog should take precedence, and the BES should write an <del>error</del>([[User:Jimg\|Jimg]]) warning message regarding this to it's logs.
	# Access to the child catalogs should be seamless. In other words using the root catalog should allow one to exercise this command:		# Access to the child catalogs should be seamless. In other words using the root catalog should allow one to exercise this command:
	#:: <font size="2"><code><bes:setContainer name="catalogContainer" space="root">~~/data~~/rdh/CTD</bes:setContainer></code></font>		#:: <font size="2"><code><bes:setContainer name="catalogContainer" space="root">/rdh/CTD</bes:setContainer></code></font>
	#:Which should be setting the container to use the CTD dataset in the RDH catalog in the above example.		#:Which should be setting the container to use the CTD dataset in the RDH catalog in the above example.

Ndp: /* Proposed solution */

2012-04-12T16:43:28Z

Proposed solution

← Older revision		Revision as of 16:43, 12 April 2012
Line 15:		Line 15:
	== Proposed solution ==		== Proposed solution ==

	Create a BES meta-catalog (the catalog called "root" or the "root catalog"??) which subsumes all of the catalogs in a particular BES. (Should the root catalog ~~should~~ be an extension of the catalog "catalog"??)		Create a BES meta-catalog (the catalog called "root" or the "root catalog"??) which subsumes all of the catalogs in a particular BES. (Should the root catalog be an extension of the catalog "catalog"??)

	[[File:Hyrax-2.0-Catalog.png\|800px]]		[[File:Hyrax-2.0-Catalog.png\|800px]]

Ndp: /* Proposed solution */

2012-04-12T16:43:02Z

Proposed solution

← Older revision		Revision as of 16:43, 12 April 2012
Line 15:		Line 15:
	== Proposed solution ==		== Proposed solution ==

	Create a BES meta-catalog (the catalog called "root" or the "root catalog"??) which subsumes all of the catalogs in a particular BES. ~~The~~ root catalog should be an extension of the catalog "catalog".		Create a BES meta-catalog (the catalog called "root" or the "root catalog"??) which subsumes all of the catalogs in a particular BES. (Should the root catalog should be an extension of the catalog "catalog"??)

	[[File:Hyrax-2.0-Catalog.png\|800px]]		[[File:Hyrax-2.0-Catalog.png\|800px]]

Ndp: /* Proposed solution */

2012-04-12T15:31:03Z

Proposed solution

← Older revision		Revision as of 15:31, 12 April 2012
Line 15:		Line 15:
	== Proposed solution ==		== Proposed solution ==

	Create a ~~master~~ BES catalog (the catalog called "root" or the "root catalog"??) which subsumes all of the catalogs in a particular BES. The root catalog should be an extension of the catalog "catalog".		Create a BES meta-catalog (the catalog called "root" or the "root catalog"??) which subsumes all of the catalogs in a particular BES. The root catalog should be an extension of the catalog "catalog".

	[[File:Hyrax-2.0-Catalog.png\|800px]]		[[File:Hyrax-2.0-Catalog.png\|800px]]

Jimg: /* Proposed solution */

2012-04-12T14:41:53Z

Proposed solution

← Older revision		Revision as of 14:41, 12 April 2012
Line 23:		Line 23:
	# It should inject into the top level catalog a "node" for each of the other catalogs in use.		# It should inject into the top level catalog a "node" for each of the other catalogs in use.
	# The name of these child catalog nodes should be the name of the catalog (or be configurable better yet)		# The name of these child catalog nodes should be the name of the catalog (or be configurable better yet)
	# If the child catalog name conflicts with one of the file system holdings then the catalog should take precedence, and the BES should write an error message regarding this to it's logs.		# If the child catalog name conflicts with one of the file system holdings then the catalog should take precedence, and the BES should write an <del>error</del>([[User:Jimg\|Jimg]]) warning message regarding this to it's logs.
	# Access to the child catalogs should be seamless. In other words using the root catalog should allow one to exercise this command:		# Access to the child catalogs should be seamless. In other words using the root catalog should allow one to exercise this command:
	#:: <font size="2"><code><bes:setContainer name="catalogContainer" space="root">/data/rdh/CTD</bes:setContainer></code></font>		#:: <font size="2"><code><bes:setContainer name="catalogContainer" space="root">/data/rdh/CTD</bes:setContainer></code></font>

Ndp at 02:46, 12 April 2012

2012-04-12T02:46:03Z

← Older revision		Revision as of 02:46, 12 April 2012
Line 39:		Line 39:
	[[User:Ndp\|ndp]] 19:03, 11 April 2012 (PDT)		[[User:Ndp\|ndp]] 19:03, 11 April 2012 (PDT)
	* It seems like it might be pretty cool to allow the root catalog to use any of the catalogs as "root" and map the others into the top level of that. Or maybe even map the others into not just the top level (maybe that's a default) but to any path specified in a configuration of the root catalog...		* It seems like it might be pretty cool to allow the root catalog to use any of the catalogs as "root" and map the others into the top level of that. Or maybe even map the others into not just the top level (maybe that's a default) but to any path specified in a configuration of the root catalog...
	* We might consider making the root catalog ~~a configuration based thing. It could~~ be ~~configured~~ to build the root ~~catalog~~ as a collection of it's catalogs. Or it could be configured to use any one of it's catalogs as ~~the~~ root catalog and then map the others into ~~this~~ root ~~catalog~~.		* We might consider making the root catalog be configurable to build the root node as a collection of the root nodes of it's catalogs. Or it could be configured to use any one of it's catalogs as a root catalog and then map the others into it's root node.

Ndp: /* Background */

2012-04-12T02:40:19Z

Background

← Older revision		Revision as of 02:40, 12 April 2012
Line 1:		Line 1:
	== Background ==		== Background ==

	When we ~~first design~~ Hyrax the BES supported multiple catalogs. At that time the BES had file system based catalog (a.k.a. the catalog called "catalog"), and a catalog implementation for the CEDAR ([http://cedarweb.hao.ucar.edu/wiki/index.php/Main_Page Coupling, Energetics and Dynamics of Atmospheric Regions]).		When we designed Hyrax the BES supported multiple catalogs. At that time the BES had file system based catalog (a.k.a. the catalog called "catalog"), and a catalog implementation for the CEDAR ([http://cedarweb.hao.ucar.edu/wiki/index.php/Main_Page Coupling, Energetics and Dynamics of Atmospheric Regions]).


	== Problem addressed ==		== Problem addressed ==

Ndp: /* Proposed solution */

2012-04-12T02:04:57Z

Proposed solution

← Older revision		Revision as of 02:04, 12 April 2012
Line 20:		Line 20:
	[[File:Hyrax-2.0-Catalog.png\|800px]]		[[File:Hyrax-2.0-Catalog.png\|800px]]

	The root catalog should behave as follows:		;The root catalog should behave as follows -

	# At it's top level it should reveal to the world the contents of the file system catalog ("catalog") PLUS		# At it's top level it should reveal to the world the contents of the file system catalog ("catalog") PLUS
	# It should inject into the top level catalog a "node" for each of the other catalogs in use.		# It should inject into the top level catalog a "node" for each of the other catalogs in use.
Line 29:		Line 28:
	#:: <font size="2"><code><bes:setContainer name="catalogContainer" space="root">/data/rdh/CTD</bes:setContainer></code></font>		#:: <font size="2"><code><bes:setContainer name="catalogContainer" space="root">/data/rdh/CTD</bes:setContainer></code></font>
	#:Which should be setting the container to use the CTD dataset in the RDH catalog in the above example.		#:Which should be setting the container to use the CTD dataset in the RDH catalog in the above example.

			; How do we determine what catalogs are present?
			: I am thinking that although run time discovery from some registry would be cool, that's probably more practical in Java land. We probably should use the configuration of the root catalog to define all of the catalogs that it will subsume.

	== Rationale for the solution ==		== Rationale for the solution ==

Ndp: /* Discussion */

2012-04-12T02:03:51Z

Discussion

← Older revision		Revision as of 02:03, 12 April 2012
Line 38:		Line 38:
	[[User:Ndp\|ndp]] 19:03, 11 April 2012 (PDT)		[[User:Ndp\|ndp]] 19:03, 11 April 2012 (PDT)
	* It seems like it might be pretty cool to allow the root catalog to use any of the catalogs as "root" and map the others into the top level of that. Or maybe even map the others into not just the top level (maybe that's a default) but to any path specified in a configuration of the root catalog...		* It seems like it might be pretty cool to allow the root catalog to use any of the catalogs as "root" and map the others into the top level of that. Or maybe even map the others into not just the top level (maybe that's a default) but to any path specified in a configuration of the root catalog...
	* We might consider making the root catalog a configuration based thing. It could be configured to build the root catalog as a collection of it's catalogs. Or it could be configured to use any one of it's catalogs as the root catalog and then map the others into this root catalog.		* We might consider making the root catalog a configuration based thing. It could be configured to build the root catalog as a collection of it's catalogs. Or it could be configured to use any one of it's catalogs as the root catalog and then map the others into this root catalog.
	~~; How do we determine what catalogs are present?~~
	: I am thinking that although run time discovery from some registry would be cool, that probably more practical in Java land. We probably should use the configuration of the root catalog to define all of the catalogs that it will subsume.