Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-30918

Historical data in Analytics

    XMLWordPrintable

Details

    Description

      As a user I would like to analyze historical data with Couchbase Analytics. To do so, Analytics service would need the ability to store data that is no longer in the data service.

      This ticket is to track all customers requesting this feature to understand the market demand.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Moved Matt Ingenthron comments from CBSE to the MB.

            Couchbase is somewhat unique with our TTL.

            I don't have a specific use case, but I would expect that there are use cases for being able to easily express:

            • Expired along with live data
            • Expired data only
            • Live data only
            • The above with particular date ranges, like when it expired or when it was created

            One particular aspect of this is that there are some environments where an item might be created, then deleted, and when recreated it could actually be totally different!

            Glad to chat through any of these ideas rattling in my head Sachin Smotra when you get to writing the PRD.

            sachin.smotra Sachin Smotra (Inactive) added a comment - Moved Matt Ingenthron comments from CBSE to the MB. Couchbase is somewhat unique with our TTL. I don't have a specific use case, but I would expect that there are use cases for being able to easily express: Expired along with live data Expired data only Live data only The above with particular date ranges, like when it expired or when it was created One particular aspect of this is that there are some environments where an item might be created, then deleted, and when recreated it could actually be totally different! Glad to chat through any of these ideas rattling in my head Sachin Smotra when you get to writing the PRD.

            One of the ideas I've been thinking about is having a tiered approach to storing data for Analytics.

            Tier 1 - KV (shadow in Analytics)
            Tier 2 - KV + Additional data that was removed from KV nodes since it was not needed for operational access
            Tier 3 - External storage like HDFS, S3, Azure BLOB Store, Snowflake etc

            I have not vetted this with customers yet but there are questions coming in on the ability to analyze more than what is in KV.

            sachin.smotra Sachin Smotra (Inactive) added a comment - One of the ideas I've been thinking about is having a tiered approach to storing data for Analytics. Tier 1 - KV (shadow in Analytics) Tier 2 - KV + Additional data that was removed from KV nodes since it was not needed for operational access Tier 3 - External storage like HDFS, S3, Azure BLOB Store, Snowflake etc I have not vetted this with customers yet but there are questions coming in on the ability to analyze more than what is in KV.

            People

              till Till Westmann
              sachin.smotra Sachin Smotra (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty