Details
-
Bug
-
Resolution: Fixed
-
Critical
-
4.0.0
-
Security Level: Public
-
Untriaged
-
Unknown
Description
Currently, GSI client runs in Query process. However, to avoid circular dependency, it cannot directly import Query loggers.
To solve this, Query can specify a bare interface and pass a pointer to logger when instantiating GSI client.
Alternate approach is to have a SetLogLevel() call on GSI client, so the client can change verbosity appropriately.
Please reassign to component=secondary-index when the API has been added and stubbed, we will wire it up appropriately.
Attachments
Issue Links
| For Gerrit Dashboard: MB-14296 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 52412,2 | For MB-14296. Normalize logging levels to uppercase before exposing them to GSI client. | master | query | Status: MERGED | +2 | +1 |
| 52414,1 | For MB-14296. Add API for setting log level for query indexers in the query process, including GSI client. | master | indexing | Status: MERGED | +2 | +1 |
| 52416,2 | For MB-14296. Add SetLogLevel() API for query indexers in the query process, including GSI client. | master | query | Status: MERGED | +2 | +1 |
| 52419,1 | For MB-14296. Add API for setting log level for query indexers in the query process, including GSI client. | unstable | indexing | Status: ABANDONED | +2 | 0 |
| 52740,2 | MB-14296: Make GSI client follow Query log levels | unstable | indexing | Status: MERGED | +2 | +1 |