[BUG]Lightgbm classifier cannot get training results after setting verbosity=1 & isProvideTrainingMetric=True

SynapseML version

1.4.0

System information

• Language version (e.g. python 3.8, scala 2.12):
  scala 2.1.2, python3.10.2
• Spark Version (e.g. 3.4.1):
  3.4.1
• Spark Platform (e.g. Synapse, Databricks):
  Databricks

Describe the problem

cannot see the training results or loss curve after setting verbosity and isProvideTrainingMetric

Code to reproduce issue

lgbm_assembler = VectorAssembler(inputCols=feature_cols, outputCol="features")
lgbm = LightGBMClassifier(
    objective="binary",
    numIterations=100,
    learningRate=0.1,
    isUnbalance=True,
    featuresCol="features",
    labelCol="label",
    isProvideTrainingMetric=True, 
    metric="auc",
    verbosity=1
)

pipeline = Pipeline(stages=[lgbm_assembler, lgbm])
model = pipeline.fit(train_data)
predictions = model.transform(val_data)

Other info / logs

No response

What component(s) does this bug affect?

• area/cognitive: Cognitive project
• area/core: Core project
• area/deep-learning: DeepLearning project
• area/lightgbm: Lightgbm project
• area/opencv: Opencv project
• area/vw: VW project
• area/website: Website
• area/build: Project build system
• area/notebooks: Samples under notebooks folder
• area/docker: Docker usage
• area/models: models related issue

What language(s) does this bug affect?

• language/scala: Scala source code
• language/python: Pyspark APIs
• language/r: R APIs
• language/csharp: .NET APIs
• language/new: Proposals for new client languages

What integration(s) does this bug affect?

• integrations/synapse: Azure Synapse integrations
• integrations/azureml: Azure ML integrations
• integrations/databricks: Databricks integrations

Start by reproducing the provided LightGBMClassifier pipeline with isProvideTrainingMetric=True and verbosity=1 in the stated Python, Scala, Spark, and Databricks setup. Then trace how training metrics and verbosity are handled in the LightGBM model integration; done means the training results or loss curve are available after fitting. No source file or test is named in the issue.