Too few changes retrieved from SG

[Héloïse Rostan]

Hi,
If I add a user with admin_channels:* before I add data to my application, all is well. However, if the user is added to SG after the data is created, too few changes are replicated. The documents do have a single channel.

Here's the output of the request for the user created before any documents are created:
Request: {"limit":5,"feed":"longpoll", "style":"all_docs","heartbeat":300000}

{
    "results": [
        {
            "seq": 1,
            "id": "_user/store",
            "changes": []
        },
        {
            "seq": 3,
            "id": "43845603-a5e3-4782-a72c-16e5a6fb2364",
            "changes": [
                {
                    "rev": "1-e4431927de1990e414fdf51b1f32eafb"
                }
            ]
        },
        {
            "seq": 5,
            "id": "fcf221fe-48fa-4b32-833f-0a5eff3f1b9c",
            "changes": [
                {
                    "rev": "1-9d84554b367c457648d1bd2915d27b02"
                }
            ]
        },
        {
            "seq": 6,
            "id": "237a0ad8-8c37-4586-be61-a309e2598c8f",
            "changes": [
                {
                    "rev": "1-9d6ef22f3ab10ab4937b1c5411212885"
                }
            ]
        },
        {
            "seq": 7,
            "id": "f90ef16e-db2a-48f7-a075-9a1cb7bb53ce",
            "changes": [
                {
                    "rev": "1-3ad08816287156fa9feec7c9e6482624"
                }
            ]
        }
    ],
    "last_seq": "7"
}

With {"limit":5,"feed":"longpoll", "since":7, "style":"all_docs","heartbeat":300000} the queries proceed as expected to get the whole data set.

The same queries (without a "since" property), but with a user created after the documents give:

{
    "results": [
        {
            "seq": "123:3",
            "id": "43845603-a5e3-4782-a72c-16e5a6fb2364",
            "changes": [
                {
                    "rev": "1-e4431927de1990e414fdf51b1f32eafb"
                }
            ]
        },
        {
            "seq": "123:5",
            "id": "fcf221fe-48fa-4b32-833f-0a5eff3f1b9c",
            "changes": [
                {
                    "rev": "1-9d84554b367c457648d1bd2915d27b02"
                }
            ]
        },
        {
            "seq": "123:6",
            "id": "237a0ad8-8c37-4586-be61-a309e2598c8f",
            "changes": [
                {
                    "rev": "1-9d6ef22f3ab10ab4937b1c5411212885"
                }
            ]
        },
        {
            "seq": "123:7",
            "id": "f90ef16e-db2a-48f7-a075-9a1cb7bb53ce",
            "changes": [
                {
                    "rev": "1-3ad08816287156fa9feec7c9e6482624"
                }
            ]
        },
        {
            "seq": "123:8",
            "id": "846241d5-b29b-415b-8308-627928af4758",
            "changes": [
                {
                    "rev": "1-ba8370ca4d89c04bd7a9cbedefa5f01f"
                }
            ]
        }
    ],
    "last_seq": "123:8"
}

I would expect to get the same output as for the first user. Proceeding with the requests gives a much smaller data set than with the first user.

I'm using a self-compiled SG from 77900d8 as I was hoping that a fix apparently applied for issue #314would resolve this issue.

Thanks for any help you can provide,

[Jens Alfke]

> On Aug 1, 2014, at 2:44 AM, Héloïse Rostan <rostan....@gmail.com> wrote:
>
> I would expect to get the same output as for the first user.

The output you’ve shown is effectively identical for both users. Only the sequences (“seq” properties) are different. The sequences with a “:” in them are part of the fix for #314; they’re used to indicate older entries that are being back-filled because the user got added to a channel. It’s weird that they’re being used in this case, though, because those entries should appear in the feed normally since you didn’t give a since= value.

> Proceeding with the requests gives a much smaller data set than with the first user.

How does it proceed after that?

Could you file this as a bug report, please?

—Jens