tpch | TPC-H benchmark , specific for mysql | SQL Database library

You would use percentile_cont() to get a percentage of some ordered value. For instance, if you had a population column for the region, then you would calculate the median population as:

In the end I just installed sqlplus and ran the command from there

it stored all the data in partition-0

That doesn't mean it's not working. Just means that the hashes of the keys ended up in the same partition.

If you want to override the default partitioner, you need to define your own Partitioner class to parse the message and assign the appropriate partition, then set partitioner.class in the Producer properties

I want all unique key(deviceID) will store in different partition

Then you would have to know your compete dataset ahead of time to create N partitions for N devices. And what happens when you add a completely new device?

If you already have a topic, you should skip to step 3 where it actually sets up the topics to query via Presto

kafka-tpch load creates new topics with the specified prefix

Docker has an unusual feature where, under some specific circumstances, it will populate a newly created volume from the image. You should not rely on this functionality, since it completely ignores updates in the underlying images and it doesn't work on Kubernetes.

In your Kubernetes setup, you create a new empty PersistentVolumeClaim, and then mount this over your actual data in both the init and main containers. As with all Unix mounts, this hides the data that was previously in that directory. Nothing causes data to get copied into that volume. This works the same way as every other kind of mount, except the Docker named-volume mount: you'll see the same behavior if you change your Compose setup to do a host bind mount, or if you play around with your local development system using a USB drive as a "volume".

You need to make your init container (or something else) explicitly copy data into the directory. For example:

I got to put it to work based on this answer https://stackoverflow.com/a/55139221/2096986 and the documentation. The first thing is that I had to use StatefulSet instead of Deployment. With this I can set the Pod IP to be stateful. Something that was not clear is that I had to set the Service to use clusterIP: None instead of type: ClusterIP. So here is my service:

The container in your pod exited with status 0 which means that the command in your container has successfully finished. You have not specified any restartPolicy for your container so the default is Always. Since your container finished - it will be restarted due to it's restart policy (actually you cannot even change that when using a deployment - it is always Always.

The deployment should be used when you have some long running processes and you want to make sure that all instances of those processees are up and can be rolled out to new versions if needed.

For one hit processes that do something and then quit - you might better use Jobs.

I had two problems with my configurations. First the Dockerfile was not copying the explore-flink.jar to the right location. Second I did not need to mount the volume job-artifacts-volume on the Kubernetes file jobmanager-job.yaml. Here is my Dockerfile:

String intern() saved me. I did intern on every string before storing it in my maps and that worked like a charm.