Skip to content

No possibility to force payload belong to the namespace #87

@kemoc

Description

@kemoc

How to declare which namespace to use for this case?:

Schema:

    {
        "namespace": "sim.events",
        "type": "record",
        "name": "SIMEvent",
        "fields": [
            {
                "name": "id",
                "type": {
                    "type": "string",
                    "logicalType": "uuid",
                    "doc": "UUID7"
                }
            },
            {
                "name": "payload",
                "type": [
                    
                    {
                        "type": "record",
                        "name": "Barred",
                        "fields": [
                             {
                                "name": "customer_status",
                                "type": "string"
                            },
                            {
                                "name": "msisdn",
                                "type": [
                                    "null",
                                    "string"
                                ]
                            }
                        ]
                    },
                    {
                        "type": "record",
                        "name": "Unbarred",
                        "fields": [
                            {
                                "name": "customer_status",
                                "type": "string"
                            },
                            {
                                "name": "msisdn",
                                "type": [
                                    "null",
                                    "string"
                                ]
                            }
                        ]
                    }
                  ]
              }
        ]
    }

every time message.payload is in Kafka (even i sends Unbarred event):
sim.events.Barred

if i know in Java that declaration is possible

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions