JSONConverter | JSONConverter is a desktop application | JSON Processing library

Json.NET basically just calls Activator.CreateInstance(ConverterType, ConverterParameters) ^[1] so the converter parameters are passed into the converter's constructor. You can remember them there and use them in ReadJson() and WriteJson() e.g. like so:

Is there a preferred way to deal with a LocalTime that represents a 24 hours span?

It's worth taking a step back and separating different concepts very carefully and being precise. A LocalTime doesn't represent a 24 hour span - it's just a time of day. Two LocalTime values could effectively represent a 24 hour span without reference to a specific date, yes.

If you can possibly change your JSON to use 00:00:00, and then treat a "start==end" situation as being the full day, that's what I'd do. That does mean, however, that you can never represent an empty period.

Now, in terms of whether you should use a start and duration... that really depends on what you're trying to model. Are you trying to model a start time and an end time, or a start time and a duration? So far you've referred to the whole day as "a 24 hour span" but that's not always the case, if you're dealing with time zones that have UTC offset transitions (e.g. due to daylight saving time).

Transitions already cause potential issues with local intervals like this - if you're working on a date where the local time "falls back" from 2am to 1am, and you've got a local time period of (say) 00:30 to 01:30, then logically that will be "true" for an hour and a half of the day:

• 00:00-00:30: False
• 00:30-01:30 (first time): True
• 01:30-02:00 (first time): False
• 01:00-01:30 (second time): True
• 01:30-02:00 (second time): False
• 02:00-00:00 (next day): False

We don't really know what you're doing with the periods, but that's the sort of thing you need to be considering... likewise if you represent something as "00:00 for 24 hours" how does that work on a day which is only 23 hours long, or one that is 25 hours long? It will very much depend on exactly what you do with the data.

I would adopt a process of:

• Work out detailed requirements, including what you want to happen on days with UTC offset transitions in the specific time zone (and think up tests at this stage)
• Extract the logical values from those requirements in terms of Noda Time types (with the limitation that no, we unfortunately don't support 24:00:00 as a LocalTime)
• Represent those types in your JSON as closely as possible
• Make your code follow your requirements documentation as closely as possible, in terms of how it handles the data

Here's what I ended up with. It turns the type into a generic object (where the properties have to be of the valueType. Note that I already have enums serialize as strings, so this may not be appropriate for other people.

The Connect container starts Connect Distributed Server already. You should use HTTP and JSON properties to configure the Elastic connector rather than exec into the container shell and issue connect-standalone commands which default to using a broker running in the container itself.

Similarly, the Elastic quickstart file expects Elasticsearch running within the Connect container, by default

If the URL is in A1 of the active sheet you could use this.

You can do this with a generic custom JsonConverter such as the following:

System.Text.Json does not make the parent property name, or more generally the path to the current value, available inside JsonConverter.Read(). This information is tracked internally -- it's in ReadStack.JsonPath() -- but ReadStack is internal and never passed to applications code.

However, as explained in Registration sample - [JsonConverter] on a property, you can apply your MyStringJsonConverter directly to public string Body { get; set; } by using JsonConverterAttribute:

The error is not saying your driver doesn't exist, it's saying the Connector doesn't. Scan over your error for each PluginDesc{klass=class and you'll notice the connector.class you're trying to use isn't there

The latest Kafka Connect images from Confluent include no connectors, outside of those pre-bundled with Kafka (and some ones from Control Center, which aren't really useful), so you must install others on your own - described here

If you want to follow the 5.0 documentation, use the appropriate tagged docker image rather than latest (the old images do have the connectors installed)

Also, you would need to place the jdbc driver directly into the jdbc connector folder for it to properly be detected on the classpath; it is not a "plugin" in Connect terminology. The above link also shows an example of this

This answer by Damien_The_Unbeliever to Why when return interface in a web api method, I get the values of inherited class with interface values? is old but apparently still applies to ASP.NET Core 3.1:

By the time it hits the Json serializer, it doesn't care what the return type of the method was. All it knows is "I have this object, let's see what I can do with it".

Thus your converter isn't called because the actual, concrete type being returned isn't IProduct and so the base class implementation JsonConverter.CanConvert(objectType) returns false: