Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-developer-preview-4
    • Fix Version/s: bug-backlog
    • Component/s: view-engine
    • Security Level: Public
    • Labels:
    • Environment:
      n/a
    • Triage:
      Untriaged

      Description

      Views are updated asynchronously. There is no atomic guarantee that after I insert an item, it will show up in affecting Views if I query them immediately after. Currently, it will only show up when the value hits the hard disk. Stale=false currently means "among all the values that have already hit the disk, do not give me stale data". I have been reading your forums and a lot of users seem to be getting confused by this.

      I would suggest one of the two things:
      1) make stale=false force get everything in the working set. i don't see why you have to wait until the value hits the disk before you are able to include it in a view... but it probably has to do with something internal. perhaps a redesign? also: what happens if i use a memcached bucket? can you even use views? there is no persist stage with memcached buckets so when would you be able to query the view? (i have no current interest in using memcached buckets but am just wondering)
      2) stop using the word stale altogether. change it to something along the lines of "not outdated but already persisted data" (that is what your current implementation of stale means)

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

        Activity

        Hide
        d3fault d3fault added a comment -

        Also, I have heard about 'observe' already. While I think it will help the problem somewhat and definitely is handy functionality, a clarification of the word 'stale' will go a lot further in terms of improving usability.

        Show
        d3fault d3fault added a comment - Also, I have heard about 'observe' already. While I think it will help the problem somewhat and definitely is handy functionality, a clarification of the word 'stale' will go a lot further in terms of improving usability.
        Hide
        dipti Dipti Borkar added a comment -

        thank you for the feedback d3fault

        Show
        dipti Dipti Borkar added a comment - thank you for the feedback d3fault
        Hide
        d3fault d3fault added a comment -

        I would like to remove #1 from the two suggestions. After more thought, I think it is impossible to perform because of the CAP theorem requirements. Go with #2 :-P

        Show
        d3fault d3fault added a comment - I would like to remove #1 from the two suggestions. After more thought, I think it is impossible to perform because of the CAP theorem requirements. Go with #2 :-P
        Hide
        vmx Volker Mische added a comment -

        In 3.0 stale=false also includes the in-memory items.

        Show
        vmx Volker Mische added a comment - In 3.0 stale=false also includes the in-memory items.

          People

          • Assignee:
            dipti Dipti Borkar
            Reporter:
            d3fault d3fault
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes