too many logs are printed when calling GraphStorageClient.scan_vertex().

[ysjiao]

when GraphStorageClient.scan_vertex() is called, to many logs as follows. I've tried to set leve of logging, but it doesn't work.

[CPWstatic]

Which loglevel is set?

[critical27]

@Sophie-Xie ask the colleague who is responsible for python or java client

[Sophie-Xie]

@Sophie-Xie ask the colleague who is responsible for python or java client

@Aiee is the owner of python client, @klay-ke is the owner of java client.

[klay-ke]

@ysjiao which client are you using? Java, go or python?

[ysjiao]

python @klay-ke

[Aiee]

@ysjiao What's the log level when you encounter the problems? Did you set --local-config == true in your config files?

[ysjiao]

@Aiee I want use logging.getLogger('nebula2').setLevel(logging.WARNING) to control the log level of nebula2-python，while other scripts using DEBUG. Should I do the both things: 1) set --local-config == true in nebula-metad.conf ， 2) set logging.getLogger('nebula2').setLevel(logging.WARNING) in my scripts

[etern]

@Aiee it's a design flaw of the python client
A module specific logger should always be used, so users got a chance to control nebula logging.
But now, logging.debug is used directly, it's root logger, like this one
Just use a logger like this

[HarrisChu]

transfer to nebula-python