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

kt group usability #122

Open
sdahlbac opened this issue Apr 20, 2021 · 0 comments
Open

kt group usability #122

sdahlbac opened this issue Apr 20, 2021 · 0 comments

Comments

@sdahlbac
Copy link

sdahlbac commented Apr 20, 2021

I might be missing something but do I really need to specify both -topic and -group in order to get reasonable results?

I.e.

kt group -topic prod_m3_13_4.service_assignment.updates -group prod_fieldops_13_4_work_order_tx
found 3 brokers
found 1 groups
found 1 topics
found partitions=[0 1 2] for topic=prod_m3_13_4.service_assignment.updates
{
  "name": "prod_fieldops_13_4_work_order_tx",
  "topic": "prod_m3_13_4.service_assignment.updates",
  "offsets": [
    {
      "partition": 0,
      "offset": 2176982,
      "lag": 0
    },
    {
      "partition": 2,
      "offset": 2172919,
      "lag": 0
    },
    {
      "partition": 1,
      "offset": 2167544,
      "lag": 0
    }
  ]
}

but if I omit e.g. the -group it seems like its doing a cross-join of topics and group and returning a bunch of bogus combinations, e.g. (kt group -topic prod_m3_13_4.service_assignment.updates)

{
  "name": "prod_fieldops_13_4_individual_meter_transaction_history_tx",
  "topic": "prod_m3_13_4.service_assignment.updates",
  "offsets": [
    {
      "partition": 0,
      "offset": null,
      "lag": null
    },
    {
      "partition": 1,
      "offset": null,
      "lag": null
    },
    {
      "partition": 2,
      "offset": null,
      "lag": null
    }
  ]
}
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