Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-18906

Lower Logging for "Using direct SQL"

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0
    • Component/s: None
    • Labels:

      Description

      https://github.com/apache/hive/blob/4047befe48c8f762c58d8854e058385c1df151c6/standalone-metastore/src/main/java/org/apache/hadoop/hive/metastore/MetaStoreDirectSql.java#L181

      2018-02-26 14:32:50,620  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-199]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:33:09,566  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-172]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:33:43,170  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-172]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:33:46,301  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-199]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:34:16,966  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-172]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:34:18,072  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-196]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:34:25,064  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-199]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:34:51,781  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-172]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:35:04,685  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-199]: Using direct SQL, underlying DB is MYSQL
      2018-02-26 14:35:26,689  INFO  org.apache.hadoop.hive.metastore.MetaStoreDirectSql: [pool-4-thread-172]: Using direct SQL, underlying DB is MYSQL
      

      I wouldn't mind knowing this information when the service starts up and detects that there is a Direct SQL compatible database, but I don't need to know about this every time.

      Please lower to debug level logging and parameterize with SLF4J. Direct SQL is a performance thing and not something I care about during the normal course of operation (unless there is an error which would presumably be covered by an error logging message).

        Attachments

          Activity

            People

            • Assignee:
              asinkovits Antal Sinkovits
              Reporter:
              belugabehr David Mollitor
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: