Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Not A Problem
-
Fix Version/s: Initial Clearing
-
Component/s: None
-
Labels:None
Description
Hadoop and related projects the following http://wiki.apache.org/general/PreCommitBuilds
to kick off builds. However, it appears the search request used for this is not returning valid XML:
[Search Request|https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=200]
to kick off builds. However, it appears the search request used for this is not returning valid XML:
[Search Request|https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/12323182/SearchRequest-12323182.xml?tempMax=200]
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hide
Jake Farrell
added a comment -
Permalink
do you need 200 returned results from this? Setting this to a more reasonable number like 50 will return the expected results as valid xml
Show
Jake Farrell
added a comment - do you need 200 returned results from this? Setting this to a more reasonable number like 50 will return the expected results as valid xml
[~tlipcon] any problems with decreasing the number of results for the precommit build?
Show
Brock Noland
added a comment - [~tlipcon] any problems with decreasing the number of results for the precommit build?
It was set to a high number before, because we used to not sort by update time DESC. So, we needed to catch as many Patch Available JIRAs as possible. But now that we do ORDER BY updated DESC, it's probably ok to drop the limit to 50.
Show
Todd Lipcon
added a comment - It was set to a high number before, because we used to not sort by update time DESC. So, we needed to catch as many Patch Available JIRAs as possible. But now that we do ORDER BY updated DESC, it's probably ok to drop the limit to 50.
That might make sense as a work around, but shouldn't JIRA be giving us a non-200 status code if it cannot complete the request? It's only a few hundred KB of data so it's not like this must be streamed in situ.
Show
Brock Noland
added a comment - That might make sense as a work around, but shouldn't JIRA be giving us a non-200 status code if it cannot complete the request? It's only a few hundred KB of data so it's not like this must be streamed in situ.
Sounds good, I changed it to 50.
Show
Brock Noland
added a comment - Sounds good, I changed it to 50.
We have upgraded JIRA, which may (or may not) have fixed this issue. Please check whether the issue still remains, and if not, close the ticket.
Show
Daniel Gruno
added a comment - We have upgraded JIRA, which may (or may not) have fixed this issue. Please check whether the issue still remains, and if not, close the ticket.
Working with 50 and with 200, if the large result set is not needed would keep the query at 50
Show
Jake Farrell
added a comment - Working with 50 and with 200, if the large result set is not needed would keep the query at 50
+1 for closing
Show
Brock Noland
added a comment - +1 for closing