Uploaded image for project: 'OASIS Content Management Interoperability Services (CMIS) TC'
  1. OASIS Content Management Interoperability Services (CMIS) TC
  2. CMIS-768

Simplify CMIS query

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Proposals for 2.0
    • Fix Version/s: None
    • Component/s: Domain Model
    • Labels:
      None
    • Proposal:
      Hide

      One approach would be to add a new operation (FETCH?) with a different projection
      A type table could include all sub type properties and all secondary type properties as optional properties on the table.
      Secondary types could include all sub-type properties, all other aspect properties and all other document/folder/item type properties as optional (helps with heterogeneous object support)

      This would remove all "same object joins" and make it easy to get and use all properties in select, where and order by.
      You could regard the "same object joins" as implied

      Show
      One approach would be to add a new operation (FETCH?) with a different projection A type table could include all sub type properties and all secondary type properties as optional properties on the table. Secondary types could include all sub-type properties, all other aspect properties and all other document/folder/item type properties as optional (helps with heterogeneous object support) This would remove all "same object joins" and make it easy to get and use all properties in select, where and order by. You could regard the "same object joins" as implied

      Description

      This follows on from CMIS-758 where some discussion took place related to query and over lap with bulk get.

      There are 3 main issues with CMIS query that I see:

      1) Now that we have secondary types, joining to all the secondary types you may wish to use is cumbersome
      You also have to left outer join to any specific sub-types for which you may want properties.

      2) To batch fetch all properties as part of a query requires that you know before hand what secondary types are applied to build the complex query above
      While it may be possible to get the ids and use the new batch operations it would be good to get all you want in one shot.

      3) To get heterogeneous objects may require several calls for folders, documents, items
      (I am not sure if we have considered selecting a secondary type and then outer joining to the base types - I would like to make that easy too)

      An example use case for both would be to generate a dynamic folder/view of documents and folders defined by a query.
      To support this the query would have similar requirements to listing children of a folder.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              andy.hind Andy Hind (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: