paging support in documentum?

Hi experts, I am new with Documentum and trying to execute a query. Doing this straightforward without setting any starting index and max result counts

I just get 100 results back - which I guess is the default limitation as specified in the configuration within the documentum jar files.

That's why I tried to implement paging (using the attached code ) where I execute a search with having a page size of (default 100) and when I get back #records >= page size then I increment the starting index and execute the query again.

Unfortunately using this approach I get (with my system) 100 records back with the first search execution and with the next one I get 0 records.

If a setMaxResultCount with e.g. 1000 then I get back 326 records (in my system) which is what a SQL Query

select count(*) from dm_type_s

also gives and which is the total number of records.

So I guess I am missing something here? What I want is to get back all objects of a given type no matter which restrictions are set on the system, so how can I archive this?

How does the paging mechanism work?

regards, Chris

TypeAnalyzer.java

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

aflowers001

For the query service, unlike the search service, there is no asynchronous concept hence you execute and get results, where as the search service has the ability to deal with Documentum and non Documentum result sets and thus allows a fire and poll model.

For queries where you want to use paging you can execute it once witha null query id and use the query id returned from the first call to get further 'paged' results.

It's all of the SDK documentation and there are some good examples in the SDK sample source code,

All comments

aflowers001

Change to using the Query Service as opposed to the Search Service. (I think there are posts in these forums and elsewhere about when/where to use one over the other)

The Search Service is intended for Full Text searches whereas the Query Service is what you should use for 'simple' DQL querying.

There are example of using the query service provided with the SDK samples.

christoph.rettig@gmail.com

Hi Andy, this was a good hint: Once I have have rewritten my search to use query service (and after changing a few different things too) the paging works fine.

I hope I can ask you a two more questions on this:

(a) with the search service I have set a query id like

execution.setQueryId(queryId)

but when I do this with the query service I get an exception "Caused by: java.lang.NullPointerException: docbaseSpecString", see

547 [main] DEBUG biz.i2z.connector.documentum.util.types.TypeAnalyzer - [41770a68:14183758888:-8000] executing query 'DfPassthroughQuery: [select * from dm_type]' (page size is 100)

2155 [main] WARN biz.i2z.connector.documentum.util.types.TypeAnalyzer - error querying all documentum types: "QUERY" action failed.

com.emc.documentum.fs.services.core.CoreServiceException: "QUERY" action failed.

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.getExceptionInstance(ClientReflectionServiceInvokerCompat60.java:176)

at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.invoke(ClientReflectionServiceInvokerCompat60.java:78)

at com.emc.documentum.fs.rt.context.impl.UcfClientInvocationHandler.invoke(UcfClientInvocationHandler.java:47)

at com.emc.documentum.fs.rt.context.impl.SoapClientInvocationHandler.invoke(SoapClientInvocationHandler.java:66)

at com.emc.documentum.fs.rt.context.impl.MtomCompatHandler60SP1.invoke(MtomCompatHandler60SP1.java:57)

at com.emc.documentum.fs.rt.context.impl.HttpSessionInvocationHandler.invoke(HttpSessionInvocationHandler.java:89)

at com.emc.documentum.fs.rt.context.impl.RemoteServiceInterfaceInvocationHandler.invoke(RemoteServiceInterfaceInvocationHandler.java:30)

at com.emc.documentum.fs.rt.context.impl.ReturnedContentTransformationHandler.invoke(ReturnedContentTransformationHandler.java:45)

at com.emc.documentum.fs.rt.context.impl.OperationOptionsHandler.invoke(OperationOptionsHandler.java:71)

at com.emc.documentum.fs.rt.context.impl.ContextThreadLocalInvocationHandler.invoke(ContextThreadLocalInvocationHandler.java:51)

at com.emc.documentum.fs.rt.context.impl.ServiceContextInvocationHandler.invoke(ServiceContextInvocationHandler.java:30)

at $Proxy20.execute(Unknown Source)

at biz.i2z.connector.documentum.util.types.TypeAnalyzer.query(TypeAnalyzer.java:205)

at biz.i2z.connector.documentum.util.types.TypeAnalyzer.queryAllTypes(TypeAnalyzer.java:82)

at biz.i2z.connector.documentum.util.types.TypeAnalyzerTest.queryAllTypes(TypeAnalyzerTest.java:46)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)

at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)

at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)

at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)

at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)

at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:82)

at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:240)

at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)

at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)

at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)

at org.junit.runners.ParentRunner.run(ParentRunner.java:300)

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:180)

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Caused by: java.lang.NullPointerException: docbaseSpecString

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.getExceptionInstance(ClientReflectionServiceInvokerCompat60.java:144)

at com.emc.documentum.fs.rt.context.impl.compat.ClientReflectionServiceInvokerCompat60.invoke(ClientReflectionServiceInvokerCompat60.java:77)

... 42 more

only when removing this line of code does the query work. Is this an error or do query ids not work using the query service?

(b) In my original implementation I do something like

for (RepositoryStatusInfo info : queryStatus.getRepositoryStatusInfos()) {

if (info.getStatus() == Status.RUNNING) {

if (retries > this.maxQueryWaitAttemps.intValue())

throw new Exception(

String.format("[%s] query is in state running and max retry count %d reached"

, queryId

, this.maxQueryWaitAttemps));

retries++;

running = true;

break;

}

running = false;

if (info.getStatus() != Status.SUCCESS)

throw new Exception(

String.format("[%s] query failed with status %s and error %s: %s"

, queryId

, info.getStatus()

, info.getErrorMessage()

, info.getErrorTrace()));

}

to check the query status of all involved repositories and re-execute the query if it is still running; I guess this re-execute only works because I have set a query id (because how should Documentum know which query to re-check).

So is this needed with the query service too or is this just with the search service?

regards, chris

aflowers001

For queries where you want to use paging you can execute it once witha null query id and use the query id returned from the first call to get further 'paged' results.

It's all of the SDK documentation and there are some good examples in the SDK sample source code,

christoph.rettig@gmail.com

Hi, so everything is clear now to me:)

Thank you very much for your help,

Chris