[INLONG-443] TubemqSourceFunction class prints too many logs problem

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Labels: pull-request-available
• Assignee: xianle cao
• Reporter: xianle cao
• Created: 05/Dec/20 06:17
• Updated: 22/Jun/22 10:10
• Resolved: 09/Dec/20 12:05

Description

When using the TubemqSourceFunction class to register the source table to consume tubemq topic data, this class prints too many info type logs, and the container log takes up a lot of disk space.

code:

```

ConsumerResult consumeResult = messagePullConsumer.getMessage();
if (!consumeResult.isSuccess()) {
LOG.info("Could not consume messages from tubemq (errcode: {}, " +
"errmsg: {}).", consumeResult.getErrCode(),
consumeResult.getErrMsg());

...

}

possible improvements：

ConsumerResult consumeResult = messagePullConsumer.getMessage();
if (!consumeResult.isSuccess()) {
if (!(consumeResult.getErrCode() == 400 || consumeResult.getErrCode() == 404 ||
consumeResult.getErrCode() == 405 || consumeResult.getErrCode() == 406 ||
consumeResult.getErrCode() == 407 || consumeResult.getErrCode() == 408)) {
LOG.info("Could not consume messages from tubemq (errcode: {}, " + "errmsg: {}).",
consumeResult.getErrCode(), consumeResult.getErrMsg());
}
...

}

```

Issue Links

• links to: GitHub Pull Request #344
• links to: GitHub Pull Request #444
• links to: GitHub Pull Request #1032