Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-1508 VIEW enhancements
  3. PHOENIX-1499

VIEW indexes are not kept in sync when parent table updated directly

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      If a physical table is updated directly then the indexes on views over the table will not be maintained. The same applies to a view that has child views. All updates should come through the child view, not the base view.

        Issue Links

          Activity

          Hide
          jamestaylor James Taylor added a comment - - edited

          Jerry Chabot - this issue is not to maintain indexes when Phoenix APIs aren't used. You could potentially write some code to do this yourself - essentially you'd need to push the same metadata that Phoenix does through your CheckAndPut calls. I've opened PHOENIX-1619 for this.

          Show
          jamestaylor James Taylor added a comment - - edited Jerry Chabot - this issue is not to maintain indexes when Phoenix APIs aren't used. You could potentially write some code to do this yourself - essentially you'd need to push the same metadata that Phoenix does through your CheckAndPut calls. I've opened PHOENIX-1619 for this.
          Hide
          jamestaylor James Taylor added a comment -

          Once this is fixed, see PHOENIX-1618 as that one would be easy to fix after that.

          Show
          jamestaylor James Taylor added a comment - Once this is fixed, see PHOENIX-1618 as that one would be easy to fix after that.
          Hide
          jchabot72 Jerry Chabot added a comment -

          Our app has an HBase table maintained using HBase client, including using CheckAndPut, etc. A view is used so our app can search the table with various search criteria. Lack of a synchronized index when updates occur to the underlying table prevents using an index. I expect one or two indices will be needed due to the flexible search criteria. It would be much appreciated if this task could be raised in priority.

          Show
          jchabot72 Jerry Chabot added a comment - Our app has an HBase table maintained using HBase client, including using CheckAndPut, etc. A view is used so our app can search the table with various search criteria. Lack of a synchronized index when updates occur to the underlying table prevents using an index. I expect one or two indices will be needed due to the flexible search criteria. It would be much appreciated if this task could be raised in priority.

            People

            • Assignee:
              Unassigned
              Reporter:
              jamestaylor James Taylor
            • Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:

                Development