tpch | Port of TPC-H dbgen to Java

To make those queries equivalent you need to use the join condition c1.c_mktsegment=c2.c_mktsegment for every row. By making it part of the OR, you are joining every row of c1 where c1.c_mktsegment = 'AUTOMOBILE' to every row of c2 regardless of what c2.c_mkrsegment is.

I believe this is what you want:

Just remove INTO. It is required in PL/SQL, but not when select is part of a cursor (in your case, that's a cursor FOR loop).

Also, you'd then reference countNationkey with cursor variable's name (QROW.countNationkey), which also means that you don't need a local variable.

So:

If using minikube you need to first mount the volume using

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: