Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Improve] [Connector-http-base]The log printing contains request message responses, which leads to the log being too large and affects problem localization. #6729

Open
3 tasks done
wssmao opened this issue Apr 18, 2024 · 1 comment

Comments

@wssmao
Copy link
Contributor

wssmao commented Apr 18, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

The log printing contains request message responses, which leads to the log being too large and affects problem localization.

Solution:
Add a configuration item to control the printing of response messages, with the switch turned off by default.

SeaTunnel Version

2.3.4

SeaTunnel Config

env {
  execution.parallelism = 1
  job.mode = "BATCH"
}

source {
   Http {
url = "http://xxx.com"
      method = "GET"
      format = "json"
      content_field = "$.data.*"
      connect_timeout_ms = 120000
      socket_timeout_ms = 600000
      schema = {
        fields {
           id = string 

        }
      }
   }
}

transform {
}

sink {
	jdbc {
		url = "jdbc:mysql://x.x.x.x/xxxx?serverTimezone=GMT%2b8"
		driver = "com.mysql.cj.jdbc.Driver"
		user = "xxxx"
		password = "xxxxx"
		query ="replace into table(id) values(?);"
	}
}

Running Command

sh seatunnel.sh --config ../config/test.conf -e local

Error Exception

NA

Zeta or Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@wssmao wssmao added the bug label Apr 18, 2024
@EricJoy2048 EricJoy2048 added improve and removed bug labels Apr 23, 2024
Copy link

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

@github-actions github-actions bot added the stale label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants