Schema differences between rust and go implementation

[askalt]

It was noticed that there is a difference between the schemas that go arrow flight adbc driver expects (in the response on get-db-schemas-request):

https://github.com/apache/arrow-go/blob/a62d36fba3b2df5be1d61a4a34fbd9bf0756676e/arrow/flight/flightsql/schema_ref/reference_schemas.go#L26-L29

Here catalog_name is nullable, but in rust we have non-nullable field:

arrow-rs/arrow-flight/src/sql/metadata/db_schemas.rs

Lines 177 to 183 in 5f0aed6

	/// The schema for GetDbSchemas
	static GET_DB_SCHEMAS_SCHEMA: Lazy<SchemaRef> = Lazy::new(|| {
	Arc::new(Schema::new(vec![
	Field::new("catalog_name", DataType::Utf8, false),
	Field::new("db_schema_name", DataType::Utf8, false),
	]))
	});

Obviously, one can return any schema from the server, but want to figure out, who is actually right and where the source of truth.