Default ViewQuery Stale - UpdateAfter?

unhuman · November 17, 2015, 10:24pm

The Java SDK (in the comments) of ViewQuery indicates that the default Stale level is Update_After. In .NET, the default is indicated to be OK. I’d argue that the default should be OK as that’s the least intensive on the Couchbase cluster.

Thoughts?

daschl · November 18, 2015, 6:44am

@unhuman actually, if you don’t specify any staleness level on the server it is UPDATE_AFTER, this is why the Java SDK indicates it is the default. So by default no staleness value is passed over to the server which then uses UPDATE_AFTER.

Where do you find that .NET always applies OK, even if you don’t set the staleness param explicitly?

unhuman · November 18, 2015, 4:27pm

Just working off of what the comment in the client says:

github.com

couchbase/couchbase-net-client/blob/master/Src/Couchbase/Views/ViewQuery.cs#L162


    _skipCount = count;
    return this;
}


/// <summary>
/// Allow the results from a stale view to be used. The default is StaleState.Ok; for development work set to StaleState.False
/// </summary>
/// <param name="staleState">The staleState value to use.</param>
/// <returns>An IViewQuery object for chaining</returns>
public IViewQuery Stale(StaleState staleState)
{
    _staleState = staleState;
    return this;
}


/// <summary>
/// Return the documents in ascending by key order
/// </summary>
/// <returns>An IViewQuery object for chaining</returns>
public IViewQuery Asc()
{

But, lower in the code, it seems to defer to whatever the server does by default:

github.com

couchbase/couchbase-net-client/blob/master/Src/Couchbase/Views/ViewQuery.cs#L483


relativeUri.Append(Design);
relativeUri.Append(ForwardSlash);


if (_development.HasValue && _development.Value)
{
    relativeUri.Append(DevelopmentViewPrefix);
}


relativeUri.Append(_designDoc);
relativeUri.Append(ForwardSlash);
relativeUri.Append(ViewMethod);
relativeUri.Append(ForwardSlash);
relativeUri.Append(_viewName);


var queryParameters = GetQueryParams();
if (!string.IsNullOrEmpty(queryParameters))
{
    relativeUri.Append(QueryOperator);
    relativeUri.Append(queryParameters);
}

Fundamentally, however, I think that querying views, by default, shouldn’t negatively affect server performance (circumventing the way views are re-indexed by the timer). If this is a server issue, can we just move the conversation to “Couchbase Server”?

ingenthr · November 23, 2015, 7:26pm

Moved this thread to the Server category based on your comment…