Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Connect/KStreams: rename existing tutorial to differentiate from upcoming tutorial

See original GitHub issue

Issue Description

JDBC source connector does not add a key but most KStreams operations require a key.

The key can be added in one of two places:

However, the naming of the first tutorial (which is already done and live) is too broad and cannot be differentiated from the new tutorial. It doesn’t specify

(a) where the key is added (KStreams vs Connect) (b) the format (SpecificAvro vs JSON)

This GH issue is to rename the existing tutorial to be more specific, to disambiguate from the other tutorial (and future tutorials)

Initial proposal:

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

colinhickscommented, Mar 19, 2020

@rmoff, given the constraints of the site structure and the existing content patterns, I think combining these tutorials makes the most sense.

With the tabs at the top of the combined tutorial in mind, we’d have:

  • Kafka Streams: #123 (done)
    • uses the JDBC connector and adds the key with KStreams
  • Kafka: #122 (open)
    • uses a connector and adds the key with SMT
  • ksqlDB #291 (open)
    • wraps a connector and adds the key with ksql

So should we reframe the existing tutorial [#123] to make it generic in referencing to the Kafka Connect source …?

Yes. If we need to add more, specific introductory material to the KStreams tutorial, we can create an optional space for that content in the template, which would be displayed only in the Kafka Streams flavor.

I guess I just label it as kafka since it technically is Apache Kafka?

Yeah, this is a bit awkward, but I agree it’s the best bet given the options.

  • shortname: connect-source-smt-set-key
  • SEO slug: add-key-to-topic-with-kafka-connect-smt
  • Tutorial title: Add a key to a stream from Kafka Connect

Seems good to me.

How does this sound overall? Thoughts @ybyzek?

rmoffcommented, Mar 26, 2020

#299 closes this.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Tutorial - Flowsheet
Tutorial. Flowsheet. We will start creating our flowsheet by adding a reactor from Model Library toolbar to the Process Flowsheet Window.
Read more >
Programmatically manage contact flows with new Amazon ...
In this blog, you learn how to leverage Amazon Connect contact flow APIs to automate create, read, update, and publish functions through a...
Read more >
Change mappings and settings for a data stream - Elastic
Update the index template used by the data stream. This ensures the new field mapping is added to future backing indices created for...
Read more >
How to Rename File in R? Using file.rename()
When renaming multiple files at a time, use Vector to specify the old and new names. To replace all files in a directory...
Read more >
Image Streams in OpenShift: What You Need to Know
If I could rename image streams, I'd probably call them image references. What does an image stream do? An image stream acts as...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found