Add the possibility to pass a lot of signatures to Bugs

NEW
Unassigned

Status

Socorro
Webapp
2 years ago
2 years ago

People

(Reporter: calixte, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
Currently it's limited to 15 signatures and I've something like 128000 signatures to pass...
That means we should be accepting data as POST, so we can pass an arbitrarily long list of signatures.
Even better, consider to talk directly to Bugzilla REST API. Then you never have to worry about information being stale. You can also retrieve confidential bugs. And you don't need a second query to turn the Bug ID into summary, resolution, status. 

But the limit is likely to be similar.
(Reporter)

Comment 3

2 years ago
(In reply to Peter Bengtsson [:peterbe] from comment #2)
> Even better, consider to talk directly to Bugzilla REST API. Then you never
> have to worry about information being stale. You can also retrieve
> confidential bugs. And you don't need a second query to turn the Bug ID into
> summary, resolution, status. 
> 
> But the limit is likely to be similar.

The problem is that it's very very long to get the bugs related to one signature with Bugzilla REST API. I already tried this approach and it's really faster to get bugs ids from Bugs and to query Bugzilla with these ids rather than to get them in making a search on crash signature field.
The reason our Bugs API is "faster" is because we have a cron job that runs every hour. 
Have you considered something like that? A cron job you maintain that slowly by slowly churns through the list of 128k signatures. 

The Bugs API was built by us to serve the webapp. To support massive data queries I think we should first reconsider how things work, or could be changed.
Component: Data request → Webapp
(Reporter)

Comment 5

2 years ago
(In reply to Peter Bengtsson [:peterbe] from comment #4)
> The reason our Bugs API is "faster" is because we have a cron job that runs
> every hour. 
> Have you considered something like that? A cron job you maintain that slowly
> by slowly churns through the list of 128k signatures. 

Yes, I thought about that in using pulse and in filling a database with "interesting" bugs.
  
> The Bugs API was built by us to serve the webapp. To support massive data
> queries I think we should first reconsider how things work, or could be
> changed.
You need to log in before you can comment on or make changes to this bug.