Welcome to MSDN Blogs Sign in | Join | Help

Confusion about Full Text Search in SSDS

When I posted the features that we delivered in Sprint 2, I mentioned Full Text Search.  This led to this blog statement "In the meantime, I’m waiting for the docs to try full-text search, which was part of Sprint 2. It’s not over until … the docs are done."

I should have mentioned in my post that we rolled out support for Full Text Indexing and Search to the backend of the service.  My fault.  So here is the clarification.  The way things work is we roll out a feature to the backend and then do the work to expose it through the web service which is SSDS.  Often this does not get worked on in the subsequent sprint.  So from now on when I talk about new features, I will just talk about features that are accessible through SSDS webservice to avoid confusion.  Sorry about this.

Published Sunday, June 22, 2008 6:48 AM by Soumitra Sengupta

Comments

# re: Confusion about Full Text Search in SSDS

Hey, it's fully understandable that you have 'back-end' and 'front-end' rollouts that might be 'out-of-sync' from the user perspective. But *please* keep us posted on both aspects, OK?  

Knowing that an item is in the back-end, even if it means we'll need to wait a bit before it's exposed to clients, is still intersting news.

Sunday, June 22, 2008 1:06 PM by mamund

# re: Confusion about Full Text Search in SSDS

Mike,

I agree wholeheartedly.

Cheers,

--rj

Sunday, June 22, 2008 2:22 PM by rogerj

# re: Confusion about Full Text Search in SSDS

Thanks Mike and Roger.  There are 4 classes of feature work we do:

a. Features exposed through the FE webservice.  The ETag support Jeff talks about is one of them.  There are 2 flavors of this - one through our REST head and other through the SOAP head

b. Feature work we do in the BE (eg. the FT index replication work we just did)

c. Feature work that enables us to operate the service efficiently.  These we call service delivery related work.  Quota enforcement, throttling, tracing, logging etc. would fall in that bucket.

d. Feature work to improve performance, reliability, scalability, geo-replication etc.

Then there are feature work which we will do as we integrate with other services from Microsoft as they come online.  You will hear more about these as time goes by.

I will call these out as we go.  Again thanks for your comments.  Appreciate it.

Sunday, June 22, 2008 2:47 PM by Soumitra Sengupta
Anonymous comments are disabled
 
Page view tracker