DataSubscriptions StartEtag best practice

[Steven Devooght]

Hi,

We are currently using data subscriptions in our application to do batch processing of documents. Our database is pretty big so we made the StartEtag of our data subscription configurable in case we need to play with this later on.

By default we want to process all documents using the subscription so we decided to default our StartEtag to Etag.Empty. This did not work however. Our next try was Etag.Empty.IncrementBy(1) with no luck either.

What did work was to pick an ETag of an existing document in the database. Note that this documents was not a document used by the data subscription.

So my question is, is ETag.Empty or Etag.Empty.IncrementBy(1) supposed to work (maybe related to Is there a difference in data subscriptions/changes api between development license and production? posted by a colleague of mine) and if not what Etag do we use if we want to process all documents knowing that our initial collection can be empty.

We are using build 30155 of RavenDB.

[Grisha Kotler]

Hi,

There was a fix for this kind of scenario (#30156-Hotfix).

How many documents in total do you have? And how many for that specific collection?

Hibernating Rhinos Ltd  

Grisha Kotler l RavenDB Core Team Developer l Mobile: +972-54-586-8647

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

RavenDB paving the way to "Data Made Simple" http://ravendb.net/

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Steven Devooght]

Hi,

In total we now have 1.659.732 documents. The collection we want to subscribe for changes now has 2488 documents.

Op woensdag 28 september 2016 11:05:48 UTC+2 schreef Grisha Kotler:

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.

[Grisha Kotler]

The lastest hotfix will fix the issue that you are seeing.

Can you try running this using the latest 3.5 build (it's based on 3.5 RC2):

https://daily-builds.s3.amazonaws.com/RavenDB-3.5.0-custom-35171.zip

This should a lot faster than 3.0 (even with the hotfix).

Hibernating Rhinos Ltd  

Grisha Kotler l RavenDB Core Team Developer l Mobile: +972-54-586-8647

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

RavenDB paving the way to "Data Made Simple" http://ravendb.net/

On 28 September 2016 at 12:38, Steven Devooght <stevend...@gmail.com> wrote:

Hi,

In total we now have 1.659.732 documents. The collection we want to subscribe for changes now has 2488 documents.

Op woensdag 28 september 2016 11:05:48 UTC+2 schreef Grisha Kotler:

Hi,

There was a fix for this kind of scenario (#30156-Hotfix).

How many documents in total do you have? And how many for that specific collection?

Hibernating Rhinos Ltd  

Grisha Kotler l RavenDB Core Team Developer l Mobile: +972-54-586-8647

Office: +972-4-622-7811 l Fax: +972-153-4-622-7811

RavenDB paving the way to "Data Made Simple" http://ravendb.net/

On 28 September 2016 at 10:32, Steven Devooght <stevend...@gmail.com> wrote:

Hi,

We are currently using data subscriptions in our application to do batch processing of documents. Our database is pretty big so we made the StartEtag of our data subscription configurable in case we need to play with this later on.

By default we want to process all documents using the subscription so we decided to default our StartEtag to Etag.Empty. This did not work however. Our next try was Etag.Empty.IncrementBy(1) with no luck either.

What did work was to pick an ETag of an existing document in the database. Note that this documents was not a document used by the data subscription.

So my question is, is ETag.Empty or Etag.Empty.IncrementBy(1) supposed to work (maybe related to Is there a difference in data subscriptions/changes api between development license and production? posted by a colleague of mine) and if not what Etag do we use if we want to process all documents knowing that our initial collection can be empty.

We are using build 30155 of RavenDB.

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+unsubscribe@googlegroups.com.

[Steven Devooght]

Thanks,

We will update Raven 3.0 to the latest hotfix. Since we're dealing with a production environment installing the RC is not an option at the moment. Once 3.5 is stable we will update.