>> >>We could let the >> user decide if using an asynchronous index is OK or not. > >Another option is if there is no synch index available but an asynch >index is available then QueryEngine should use that instead of >resorting to traversal.
Well, this is the current behavior. The query engine doesn't know which index is async. If an async index reports a reasonable cost, the it is already used. But this might not be what the user wants: Maybe having up-to-date results is important for him. So, maybe instead of "async_ok", we need a flag "async_not_ok". Regards, Thomas
