http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/JCBC-63 Couchbase Java Client There are have been several requests from users to have APIs to create and delete views from the Java (and other) SDKs. <br/> This is a MUST have for some customers and needs to be a part of the Client SDK we release prior to Beta. JCBC-63

add APIs for creating and deleting design documents for CBS 2.0

New Feature Blocker Resolved Fixed Public Michael Nitschinger Dipti Borkar Fri, 8 Jun 2012 01:31:51 -0500 Thu, 29 Nov 2012 02:58:04 -0600 Thu, 29 Nov 2012 02:58:04 -0600 1.1dp 1.1-beta library 0 2 I&#39;m in agreement. One question is do we also want this API to be involved in the view materialization process. I think the answer is probably yes, but this can be complicated since it can potentially take a very long time with little feedback. When you say View materialization process? what exactly do you mean? given that index building happens at query time, I don&#39;t think so. <br/> <br/> However, there are other APIs that may be more interesting to have. explicitly triggering compaction, configuring min time duration / min # of mutations to trigger index building. What I mean by the view materialization process is that we, in the web console, have this flow where we advise people to take their &quot;dev_aview&quot; and run a full cluster dataset query on it before publishing it to production. This way, when it&#39;s published as &quot;aview&quot;, the view will have been mostly materialized. It&#39;s a nice thing for updating a view. <br/> <br/> The reason this is complicated is that it&#39;s an HTTP request that may go for a very long, long time. I can think of a way around it (poll it with a timeout until it&#39;s fast), but it&#39;s suboptimal unless we start querying view materialization progress. Matt, what if we wait for it in a separate thread and return with a future when it&#39;s done? We just need to make the user aware that it can take a long time, and if they add a view for development that they&#39;d have to publish it separately. <br/> <br/> Another idea would be to make the &quot;let&#39;s do a full dataset query&quot; optional when the view gets published since someone may want to do that later or from the web-ui. Michael: that&#39;s effectively what we do right now since it&#39;s the query against the view that takes a long time. The design document management operations do not. The view requests are not quite done asynchronously, that&#39;s true. <br/> <br/> The main point I was raising was that the Web Console provides for functionality to execute a view before pushing it in production and workflow to take it from &quot;dev_thing&quot; to &quot;thing&quot; knowing that the view has been materialized. In the SDK, I don&#39;t think we&#39;ll try to replicate that workflow, but the same functionality is definitely available. Just to keep everyone updated, I started developing it here: <a href="http://review.couchbase.org/#/c/21380/">http://review.couchbase.org/#/c/21380/</a> this has finally been merged to master. Dependency JCBC-147 Rank 10123 Time In Status