Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1
-
Fix Version/s: 2.1
-
Component/s: None
-
Labels:None
Description
When the results are retrieved from the cache, the input parameter "query" is not properly set by the input component (because it is bypassed).
Activity
Not quite fixed in fact 
Now clustering (cached) local XML files in the tuning browser works kind of weird – when you first load and cluster an XML file you get one set of clusters, and when you just hit the "Refresh" button, you may get a different set of clusters.
This is caused by the fact that the XML file input component changes the query during the processing – on input it gets an XML file name, but if the XML file file contains the original query, the latter is passed down the chain. Unfortunately, with your fix, when replaying from cache, the original query was not restored (and file name was present instead).
I'll commit a fix for that in a second.
Now clustering (cached) local XML files in the tuning browser works kind of weird – when you first load and cluster an XML file you get one set of clusters, and when you just hit the "Refresh" button, you may get a different set of clusters.
This is caused by the fact that the XML file input component changes the query during the processing – on input it gets an XML file name, but if the XML file file contains the original query, the latter is passed down the chain. Unfortunately, with your fix, when replaying from cache, the original query was not restored (and file name was present instead).
I'll commit a fix for that in a second.
Fixed in trunk. I made a modification to LocalProcessBase to always set the query parameter in the request
context (unless it is already present).