Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

passing trigger's topic information when job execute #6256

Open
inha18minseokkim opened this issue Oct 22, 2024 · 1 comment
Open

passing trigger's topic information when job execute #6256

inha18minseokkim opened this issue Oct 22, 2024 · 1 comment

Comments

@inha18minseokkim
Copy link

          oh, there's closed issue that i looking for.. was this issue solved?

In my case, i created Kafka reader spring batch which is triggered by KEDA topic.
and i wanted to intergrate project and looking for switch~case logic.
ex)
topic-1 triggers app-1
topiic-2 triggers app-2

so i thought this below works, but closed..

template:
  spec:
    containers:
      - name: containerjobname
        image: imagefoofoo
        env:
          - name: APP_NAME
            value: "{{metametadata.foo}}"

triggers:
  - metadata:
      bootstrapServers: 'kafkabroker'
      consumerGroup: topic-1-consumer-group
      lagThreshold: '1'
      offsetResetPolicy: latest
      topic: topic-1
      metametadata:
          foo : app-1
    type: kafka

Originally posted by @inha18minseokkim in #5218 (comment)

@inha18minseokkim inha18minseokkim changed the title oh, there's closed issue that i looking for.. was this issue solved? oh, there's closed issue that i looking for.. passing trigger information when job execute Oct 22, 2024
@inha18minseokkim
Copy link
Author

i just think it would be nice for job to know which topic triggers the job in runtime, although somethings like metadata is not available. topic would be enough

@inha18minseokkim inha18minseokkim changed the title oh, there's closed issue that i looking for.. passing trigger information when job execute passing trigger's topic information when job execute Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant