CouchbaseConfig issue with filtering of properties with connectionIdentifier
Description
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
Graham Pople October 10, 2023 at 5:04 PM
good timing, I've just clicked the button on Sonatype and 3.3.2 should be available soon. Release notes update to follow tomorrow, but they should be able to grab the release today.
Yuvraj Kanwar October 10, 2023 at 4:43 PM
Hi Team, When and in what version will this improvement be available?
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Graham PopleReporter
Michael ReicheStory Points
0
Sprint
None
Fix versions
Priority
MajorInstabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Sentry
Linked Issues
Sentry
Linked Issues
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Created September 16, 2023 at 12:42 AM
Updated November 28, 2023 at 4:49 PM
Resolved November 28, 2023 at 4:49 PM
Instabug
see https://couchbasecloud.atlassian.net/browse/CBSE-15215
The issue is with the filtering of properties in CouchbaseConfig. It filters out all spark.couchbase.<property> and all the spark.couchbase.<property>:<connectionIdentifier> properties.
So when you have a connection-identified properties, you must select that connectionIdentifier, else they won't be filtered out, and the propertyloader will try to load them. Also, if you added a second set of connection-identified properties, if you selected on the first connection-identifier, then the other's properties would not be filtered.
The resulting exception is :