Hi, Gnanaprakash:
Thanks for the clarification.
Would it be possible to express the user's subscription as an additional query
clause in the query options:
http://docs.marklogic.com/search:search#opt-additional-query
In this approach, you wouldn't have to write any REST server extensions.
Hi Erik
I think I didn't explain my requirement well.
Search based on Rest (Get) should have the below steps internally
1. Rest Search --> 2. Call an external service --> 3. Get Results --> 4.
Update document --> 5. Rest Search
The main issue here is we are updating a document (subscrip
Hi, Gnanaprakash:
The best approach might be to write a resource service extension that does
steps 2 through 4 as one request. Then, when the ingestion request finishes,
do step 5 as a standard REST search request.
That way, the ingested documents will be available to all searchers at the
ear
Hi Erik,
I am having a requirement to Search based on
1. Rest API Call --> 2. Call an external service --> 3. Get Results -->
4. Ingest transformed document --> 5. Perform Rest API Search
Note: the search will be effected drastically based on step 4 (sometimes based
on condition steps 2
