Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.7-incubating
    • None
    • None

    Description

      We need to store the entity update events in some store. The search supported should return all events for a given entity id within some timerange.
      Two choices are:
      1. Existing graph db - We can create a vertex for every update with properties for entity id, timestamp, action and details. This will create disjoint vertices. The direct gremlin search is enough to retrieve all events for the entity.
      Pros - We already have configurations for graph and utilities to store/get from graph
      Cons - It will create extra data and doesn't fit the graph model

      2. HBase - Store events with key = entity id + timestamp and columns for action and details. The table scan supports the required search
      Pros - Fits the data model
      Cons - We will need the configurations and code to read and write from hbase

      In either case, we should expose an interface so that alternative implementations can be added

      Attachments

        1. ATLAS-539.patch
          21 kB
          Shwetha GS
        2. ATLAS-539-v2.patch
          29 kB
          Shwetha GS
        3. ATLAS-539-v3.patch
          30 kB
          Shwetha GS
        4. ATLAS-539-v4.patch
          30 kB
          Shwetha GS

        Activity

          People

            shwethags Shwetha GS
            shwethags Shwetha GS
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: