Thanks a lot for your response Matt. It was really helpful. -Ali
On Monday, July 21, 2014 6:02:48 PM UTC-7, Matt Ingenthron wrote: > > Hi Ali, > > Please see inline. > > > On Jul 21, 2014, at 3:10 PM, Ali <[email protected] <javascript:>> wrote: > > Hi, > > I have a few basic questions about Java SDK 2.0.0-dp2. It will be really > great if someone can help me with these questions. > > 1. Currently we are using 1.4.2 SDK but we want to use 2.0.0-dp2 to use > the N1QL features for querying. But 2.0.0-dp2 does not seem to contain the > APIs for creatinf design documents and views. What will be the best way to > proceed in this. We want to migrate to 2.0.0-dp2 wherever possible and use > 1.4.2 only where it is necessary. We are working with a maven project here. > > > That’s just a shortfall in DP2. I know Michael is working on that and > it’ll be there shortly. > > One workaround would be to use a tool like jarjar to pull both clients > into a single project. Though, it’s just an HTTP PUT, so you’re probably > just as well off implementing it. The docs cover the details > <http://docs.couchbase.com/couchbase-manual-2.5/cb-rest-api/#storing-design-documents> > . > > > 2. Do we have any documentation on how the N1QL queries use views > internally? What happens if there is no useful view associated with the > given query? Will there be a full table scan? > > > Given that N1QL is in developer preview, I wouldn’t say you should > depend on any given implementation but you can depend on the interface. > There will be suitable ways of using and defining indexes for sure… and > yes there will likely be a fall back to a full scan if there isn’t an > index. I think there has to be, right? > > I’d say for the moment, if N1QL meets your needs as a DP, you’re just > good to go. > > Hope that helps, > > Matt > > -- > Matt Ingenthron > Couchbase, Inc. > > -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
