After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 472868 - Port functionality/report: Simple-dup-finder & stack finding
Port functionality/report: Simple-dup-finder & stack finding
Status: RESOLVED FIXED
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks: ultra
 
 
Reported: 2007-09-02 16:06 UTC by Olav Vitters
Modified: 2009-08-16 20:25 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Olav Vitters 2007-09-02 16:06:04 UTC
This needs to be partly ported and mostly redesigned to 3.0. This is likely difficult.

Bugzilla/GNOME.pm needs to be ported as well

Note: instead of searching the database, the functions should be parsed when comments are added. Then an MD5 should be taken from this and stored in a column. Either in longdescs, or in another table, referencing the comment in longdescs.

Per problems with attach_data (was split up from attachments table to increase query speed), the other table probably makes sense.

The parsing should be done in AppendComment() in create() in Bugzilla/Bug.pm. Further, checksetup.pl should parse existing comments and fill the table/column. See extensions/gnome/code/install-update_db.pl.

Simple-dup-finder should first check if a stack trace can be found. If so, use the MD5 column/table. If not, use full text indexing.
Note: We'll be using Postgresql (likely), so needs to be checked if Pg FTI works when dumping the entire comment in there.

If you are interested, please say so. I can add more detail if needed.
Comment 1 Max Kanat-Alexander 2009-08-16 20:25:47 UTC
This has been done, with the traceparser extension for Bugzilla 3.4.