◆ Apache Cassandra

Retrieve all records in time range

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRetrieve all records from the 'sensor_readings' table in the 'telemetry' keyspace between…+
Retrieve all records from the 'sensor_readings' table in the 'telemetry' keyspace between '2023-10-26 08:00:00+0000' and '2023-10-26 09:00:00+0000' for the morning incident review.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore pulling the 'user_activity' records for the last hour, estimate the number of rows that…+
Before pulling the 'user_activity' records for the last hour, estimate the number of rows that will be returned and flag if it exceeds 10,000 to prevent overwhelming the client application.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to retrieve all records from 'event_log' for the last 24 hours, but the query keeps…+
A query for a time range is timing out, and I'm not sure if it's too much data or a bad query.
I'm trying to retrieve all records from 'event_log' for the last 24 hours, but the query keeps timing out. I'm afraid I'm either trying to pull too much data at once, or my query isn't optimized for the table's partitioning. I can't afford to bring down the cluster. What's the best way to diagnose this and safely retrieve the data?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe constantly struggle with slow or timing-out queries when trying to retrieve data within…+
Queries for time ranges often perform poorly or time out, impacting reporting and analytics.
We constantly struggle with slow or timing-out queries when trying to retrieve data within specific time ranges, particularly for ad-hoc analysis. This frustrates the data science team and delays critical insights. What habit should I change to consistently write more performant time-range queries and avoid these bottlenecks?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Cassandra's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.