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

Property2Index index content store strategy

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 0.6
    • query
    • None

    Description

      Following OAK-511, I've realized that it should be simple enough to further refactor the code to provide a store(&retrieve) strategy.

      The strategy could be property based (PropertyIndex), based on paths of child nodes (Property2Index), or any kind of layered structured - possibly a btree like the old PropertyIndex had.

      This spans from the idea that the UUID index doesn't really need to have a new level of child nodes, it can easily keep the paths as properties.

      The up side is that we could play with the store strategy until we find one that fits each implementation we have, or even have a dynamic strategy that changes over time with the amount of content the index has to store.

      Attachments

        1. OAK-517.patch
          20 kB
          Alex Deparvu

        Issue Links

          Activity

            People

              stillalex Alex Deparvu
              stillalex Alex Deparvu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: