feat(connector): support QualifiedReferenceSubjectNameStrategy

[xiangjinwu]

risingwave/src/connector/src/schema/schema_registry/util.rs

Lines 146 to 156 in 33a9302

	/// One schema can reference another schema
	/// (e.g., import "other.proto" in protobuf)
	#[derive(Debug, Deserialize)]
	pub struct SchemaReference {
	/// The name of the reference.
	pub name: String,
	/// The subject that the referenced schema belongs to
	pub subject: String,
	/// The version of the referenced schema
	pub version: i32,
	}

The name field is currently unused in our code base. It is dropped and assumed to always equal to the subject field by subsequent handling logic. This assumption does not hold when the producer registers with ReferenceSubjectNameStrategy=QualifiedReferenceSubjectNameStrategy rather than ReferenceSubjectNameStrategy= DefaultReferenceSubjectNameStrategy, or the human user makes up names arbitrarily not following the default.

For example, if the main protobuf file references mypackage/myfile.proto, its subject may be mypackage/myfile.proto (default) or mypackage.myfile (qualified) for the purpose of fetching from schema registry, but its name is always mypackage/myfile.proto for the purpose of compiling with protoc.

To fix, the following Vec<Subject> shall be replaced with a container with [(String, Subject)] (Vec/HashMap/BTreeMap/...).

risingwave/src/connector/src/schema/schema_registry/client.rs

Lines 179 to 183 in 33a9302

	/// get the latest version of the subject and all it's references(deps)
	pub async fn get_subject_and_references(
	&self,
	subject: &str,
	) -> SrResult<(Subject, Vec<Subject>)> {

[github-actions]

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.