Closed
Bug 972414
Opened 12 years ago
Closed 12 years ago
add export to analyzer search
Categories
(Input Graveyard :: Search, defect)
Input Graveyard
Search
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: u=analyzer c=search p=2 s=input.2014q1)
Analyzers need to be able to download the data in some structured form that they can use with other tools.
This bug covers implementing a CSV download for analyzer search data.
| Assignee | ||
Updated•12 years ago
|
| Assignee | ||
Comment 1•12 years ago
|
||
Tweaking subject to be clearer.
It might be helpful/interesting to have export explicitly require you to state you want private information in the export.
Summary: add structured download to analyzer search → add export to analyzer search
| Assignee | ||
Comment 2•12 years ago
|
||
Tossing this url in here. I think this is how I want to implement this:
https://docs.djangoproject.com/en/dev/howto/outputting-csv/
However, I'm concerned about generating massive files which could stress the system. We probably want to limit the number of rows that can be exported at once to like 1000. If we do that, we need some way to denote that we limited the export. Could be as easy as adding a row at the end along the lines of "Truncating n rows...".
| Assignee | ||
Comment 3•12 years ago
|
||
| Assignee | ||
Comment 4•12 years ago
|
||
Landed in master in https://github.com/mozilla/fjord/commit/4ffe4f0
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 5•12 years ago
|
||
Oops--meant to say "pushed to prod just now".
Updated•9 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•