[
https://issues.apache.org/jira/browse/SLING-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16195132#comment-16195132
]
Robert Munteanu commented on SLING-7169:
----------------------------------------
Anyway, taking a step back, I've been looking at the logs. Since this is Oak
1.6, this seems to be hitting the following code in {{QueryImpl}}
{code:java}
String message = "Traversal query (query without index): " +
statement + "; consider creating an index";
switch (traversal) {
case OK:
break;
case WARN:
if (!potentiallySlowTraversalQueryLogged) {
LOG.info(message);
potentiallySlowTraversalQueryLogged = true;
}
break;
case FAIL:
if (!potentiallySlowTraversalQueryLogged) {
LOG.warn(message);
potentiallySlowTraversalQueryLogged = true;
}
throw new IllegalArgumentException(message);
}
{code}
Since the message is logged at info level, the query is not aborted. And I only
see INFO messages, which means that technically the query should have been
executed:
{noformat}
02.10.2017 13:14:05.469 *INFO* [127.0.0.1 [1506939245456] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.523 *INFO* [127.0.0.1 [1506939245519] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.580 *INFO* [127.0.0.1 [1506939245577] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.642 *INFO* [127.0.0.1 [1506939245636] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.700 *INFO* [127.0.0.1 [1506939245698] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.756 *INFO* [127.0.0.1 [1506939245754] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.811 *INFO* [127.0.0.1 [1506939245809] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
02.10.2017 13:14:05.868 *INFO* [127.0.0.1 [1506939245865] GET
/testing/fullTextQuery HTTP/1.1] org.apache.jackrabbit.oak.query.QueryImpl
Traversal query (query without index): SELECT * FROM [nt:base] AS s WHERE
CONTAINS(s.*, $queryText); consider creating an index
{noformat}
Does this mean that full text queries don't work in traversal mode or is there
something else going on here?
> FullTextIndexingTest sometimes fails with a timeout
> ---------------------------------------------------
>
> Key: SLING-7169
> URL: https://issues.apache.org/jira/browse/SLING-7169
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Reporter: Robert Munteanu
> Labels: sling-IT
> Attachments: SLING-7169-logs.tar.gz
>
>
> The test fails maybe 1 in 10 runs. I could reproduce this locally by running
> many times. I've also seen it once on Jenkins.
> **Old description below**
> After upgrading the launchpad to commons.threads 3.2.10 the
> FullTextIndexingTest failed ( [build
> 1547|https://builds.apache.org/job/sling-launchpad-testing-1.8/1547/] ).
> I also reproduced it once locally.
> [~kwin] - since the commons.threads release is the potential root cause, can
> you please take a look at the failure and see if it's related?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
