You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Brian Foster (JIRA)" <ji...@apache.org> on 2010/12/07 01:24:12 UTC
[jira] Created: (OODT-69) Filemgr Catalogs should loaded Element
based off Element name and ProductType
Filemgr Catalogs should loaded Element based off Element name and ProductType
-----------------------------------------------------------------------------
Key: OODT-69
URL: https://issues.apache.org/jira/browse/OODT-69
Project: OODT
Issue Type: Bug
Components: file manager
Affects Versions: 0.1-incubating
Environment: none
Reporter: Brian Foster
Assignee: Brian Foster
Priority: Minor
Fix For: 0.2
- ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969220#action_12969220 ]
Chris A. Mattmann commented on OODT-69:
---------------------------------------
Hey Brian:
bq. but element id depends on the repository manager implemented . . . in the xml version it is typically urn:<ns>:<element_name>, however if a data source one where implemented, element id most likely would be an integer
This is not *strictly* true. In fact, you can mix and match (we have in the past, even on OCO) where we used a DataSourceCatalog, but an XML repo layer, in which case the element ID would not be an integer, it was *still* a URN. Also the scheme you propose for elements that's usually used is just *one of many possible* schemes that could be used to avoid collision.
bq. thus a user querying the filemgr would then have to be aware of which repository manager was being used; using element name / product type to determine element id hides this from the user.
Not necessarily. We could also come up with smart names for ProductTypes that avoided this collision, or even expose a query criteria method using element IDs (the way it *used* to work before you changed it :) ). That way o.a.oodt.cas.filemgr.structs.QueryCriteria would actually be a mapping of element ID to value.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-69:
----------------------------------
- push out to 0.5
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ramirez updated OODT-69:
-----------------------------
Fix Version/s: (was: 0.2)
0.3
Pushing off to 0.3 release.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.3
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-69:
----------------------------------
Fix Version/s: (was: 0.3)
0.4
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.4
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Foster updated OODT-69:
-----------------------------
Description: - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog (was:
- ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog)
Summary: Filemgr Catalogs should load Element based off Element name and ProductType (was: Filemgr Catalogs should loaded Element based off Element name and ProductType)
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968747#action_12968747 ]
Chris A. Mattmann commented on OODT-69:
---------------------------------------
Interesting. So one way to handle this might be explicitly exposing a query method that relies on element ids to differentiate the element name conflict.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968909#action_12968909 ]
Brian Foster commented on OODT-69:
----------------------------------
but element id depends on the repository manager implemented . . . in the xml version it is typically urn:<ns>:<element_name>, however if a data source one where implemented, element id most likely would be an integer . . . thus a user querying the filemgr would then have to be aware of which repository manager was being used; using element name / product type to determine element id hides this from the user.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968624#action_12968624 ]
Brian Foster commented on OODT-69:
----------------------------------
- getElementById is still there, but not useful in this case . . . file manager queries use the element names, and the DataSourceCatalog, for example, requires element id in the queries, so a remapping is done in the Catalog using the ValidationLayer to map ElementName to ElementId . . . if two ProductTypes have the same ElementName but require a different ElementId depending on the ProductType, this is where the problem arises.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968602#action_12968602 ]
Chris A. Mattmann commented on OODT-69:
---------------------------------------
Hmmm interesting.
I think we discussed this before and the idea was that ValidationLayers are intrinsically tied to the underlying Catalogs that they serve (hence the getValidationLayer() as part of the explicit o.a.oodt.cas.filemgr.catalog.Catalog interface). There used to be a method to getElementById, which should deal with this issue (an element ID could be namespaced, e.g., urn:ptype:elemid) where *ptype* is *Product Type*. This should aid in differentiating them and I think would work as a solution to this.
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Updated] (OODT-69) Filemgr Catalogs should load Element
based off Element name and ProductType
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-69:
----------------------------------
Fix Version/s: (was: 0.4)
0.5
- push to 0.5
> Filemgr Catalogs should load Element based off Element name and ProductType
> ---------------------------------------------------------------------------
>
> Key: OODT-69
> URL: https://issues.apache.org/jira/browse/OODT-69
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.5
>
>
> - ProductTypes may have Elements with same name but different meaning . . . thus using the ValidationLayer to get an element by name without taking the ProductType into consideration can cause the wrong Element ID to be sent to the underlying Catalog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira