[CORE-373] Better error reporting for queries run with concepts that don't exist Created: 02/Apr/15 Updated: 16/Mar/20 |
|
| Status: | New |
| Project: | i2b2 Core Software |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | TBD |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Nathan Graham | Assignee: | Mike Mendis |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Affects View/s: |
Query Tool
|
| i2b2 Sponsored Project/s: |
i2b2 Web Client
|
| Affects Database/s: |
All databases
|
| Affects Web Browser/s: |
All Web Browsers
|
| Participant/s: |
| Description |
|
A user reported that the i2b2 webclient showed a pop-up error message that simply said "ERROR: ERROR" when they tried to run a previous query that had worked before we refreshed our i2b2 database.
After turning on debug logging, we found a message saying: 10:44:10,938 DEBUG [edu.harvard.i2b2.crc.dao.setfinder.querybuilder.temporal.TemporalPanel] (Thread-72) Concept not found error: [\\i2b2_Visit Details\i2b2\Visit Details\Encounter Type\] We then realized that this error was expected since we had changed concept paths since the query worked. But, it would be nice to have this error message reported to the client rather than buried in a DEBUG level message on the server. i2b2 version: 1.7.04 |
| Comments |
| Comment by Janice Donahoe [ 04/Apr/18 ] |
| Needs to be reviewed by the i2b2 PMC. |