Content queries using LSCS on a project other than default project

Hi All,

TS/LS - 732

LSCS on Tomcat 6.

I want to fetch DCR content using my LSCS queries. I used below query:

http://localhost:1876/lscs/v1/document/path/templatedata/Product/SimplePromo/data/component-guide/Tanzania.xml

and it gave me the DCR content which is fine as this DCR belongs to my default project.

But I would like to fetch the DCR content in a similar manner from a project other than default project. So, I tried query as below:

http://localhost:1876/lscs/v1/document/path/templatedata/Comp-Tab/offers-detail/data/en/offer-detail.xml&project=//win2003ts721/default/main/component-guide

but I see below error:

No such resource: /lscs/v1/document/path/templatedata/Comp-Tab/offers-detail/data/en/offer-detail.xml&project=//win2003ts721/default/main/component-guide

However I can do the same query using context id as below:

http://localhost:1876/lscs/v1/document/id/85939e4e44d167a4388e44a4ca7957ab/context/c7f8aa0b1f0dd0ee9a3afae5e12d62bb

and it returns the content of the DCR from that specific project.

So, my question is:

1- why I cannot query DCR content from project other than default project using "path" identifier?

2- What is the use of the context identifier? Why I was able to query DCR content from other project using context identifier?

Thanks,

Find more posts tagged with

Comments

Kapil_sape

HI All,

I managed to figure out the mistake in my query. Below query works:

http://localhost:1876/lscs/v1/document/path/templatedata/Comp-Tab/offers-detail/data/en/offer-detail.xml?project=//win2003ts721/default/main/component-guide

So, as the project name is the first query string parameter in the query we need to use ? instead of &.

But still I would like to know what is the use of context identifier and when it is used.

Thanks,

Bowker

To the best of my knowledge....

There are two long identifiers with each search result, "id" and "context".

The "context" is the file location within the LSCSRT-Store folder. The final location Depends upon which version of LSCS you are running. In 7.4.1 (and I believe this has been true since 7.2.1 update 1) the location of the content and Index information (extended attributes) are located in a folder with the name of:

/<first three digits>/<next three digits>/<full context id>

For example:

The result:

<document id="65f100d8d319d90551b61b87275f7138" uri="/document/id/65f100d8d319d90551b61b87275f7138"

context="7994538f25c1dce70313b34a7c1b1932" path="....">

Can be pulled from the disk here:

.../LSCSRT-Store/799/453/7994538f25c1dce70313b34a7c1b1932/...

Note that in version 7.2.1 prior to update 1 the full context id was used as the primary folder and people (us included) ran into an issue with 32000+ folders in one folder. Unix doesn't allow that. Now that they break them up you won't (shouldn't) have more than 4096 folders in any one folder.

I don't believe you ever need to use it unless you are debugging something or you want to go directly to the file instead of using LSCS to return the content. I guess if you are running LSCS on the same server as LSDS you could read the file directly from disk and avoid hitting LSCS again to get the content.

Rick Poulin

Sortof echoing bowker here.. The context ID identifies the project (and other things) so it effectively builds a proper query with project parameter for you. The reason it's not frequently used is because it's hard to obtain a context ID for a particular file, but it's otherwise just a different way of asking LSCS for data.