vertica / spark-connector

This component acts as a bridge between Spark and Vertica, allowing the user to either retrieve data from Vertica for processing in Spark, or store processed data from Spark into Vertica.
Apache License 2.0
20 stars 21 forks source link

Set connection client label #495

Closed jeremyprime closed 2 years ago

jeremyprime commented 2 years ago

Summary

Set connection client label.

Description

Previously we set the APPLICATIONNAME using setClientInfo, which only set the client label on the v_monitor.sessions table. By setting the LABEL (as a connection property) the client label is set on the v_montor.sessions and dc_session_starts tables. It is important to set the client label on the dc_session_starts table to ensure we can track Spark Connector usage using the Vertica Data Collector utility.

Verified that the client label is set as expected (e.g. vspark-vs3.3.2-p-sp3.3.0) on both v_montor.sessions and dc_session_starts tables.

Related Issue

Closes #494

Additional Reviewers

@alexey-temnikov @alexr-bq @jonathanl-bq @aleximpert

codecov[bot] commented 2 years ago

Codecov Report

Merging #495 (a215d37) into main (5dcc840) will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #495   +/-   ##
=======================================
  Coverage   87.52%   87.52%           
=======================================
  Files          44       44           
  Lines        1988     1988           
  Branches      110      110           
=======================================
  Hits         1740     1740           
  Misses        248      248           
Flag Coverage Δ
unittests 87.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more