Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-6905

Query engine: support coalesce function as in-built method

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7.12, 1.8.0
    • Component/s: core, lucene, query
    • Labels:
      None

      Description

      Sometimes the content structure stores semantically similar properties at different locations (due to content evolution or different locations genuinely represent different values).

      e.g. say a content represent a real world image as ..../file1.jpg/jcr:content/file. Where jcr:content/metadata/exif:title could be title of image from exif data, jcr:content/jcr:title could be title explicitly set by user.

      While displaying a title, it probably makes sense to show jcr:title first and fallback to exif:title and then probaly to node name if nothing else works out.

      it'd would be useful to have such overlaying be conveyed to query engine too for lookup, ordering (and, of course, indexing). As a method name, sql colesce is exactly what should serve this purpose.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                catholicon Vikas Saurabh
                Reporter:
                catholicon Vikas Saurabh
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: