◆ Apache Cassandra

Implement custom Cassandra functions

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 taskImplement a custom Cassandra function named 'calculate_tax(amount, rate)' in the 'finance_ks'…+
Implement a custom Cassandra function named 'calculate_tax(amount, rate)' in the 'finance_ks' keyspace that returns 'amount * rate', and ensure it's available for use by Monday. Confirm it compiles and deploys.
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 I deploy this 'get_customer_segment(customer_id)' function to production, make it easy…+
Before I deploy this 'get_customer_segment(customer_id)' function to production, make it easy to monitor its performance. Show me how to track its execution time and resource consumption, and flag any potential bottlenecks that could impact overall database latency.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentMy new 'encrypt_field(text)' function is failing with a 'ClassCastException' when called from…+
My new 'encrypt_field(text)' function is failing with a 'ClassCastException' when called from the application, but it works in cqlsh.
My new 'encrypt_field(text)' function is failing with a 'ClassCastException' when called from the application, but it works in cqlsh. I'm afraid there's a type mismatch between the application's driver and the function's signature, or a serialization issue, and the security team needs this by end of day. What's the most likely diagnosis for this discrepancy, and what's the best next move to quickly identify and resolve the type incompatibility?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternCustom function deployments frequently cause unexpected errors or performance degradation in…+
Custom function deployments frequently cause unexpected errors or performance degradation in production.
Custom function deployments frequently cause unexpected errors or performance degradation in production, leading to urgent rollbacks and lost time. I suspect I'm not adequately testing edge cases or resource implications before release. What habit should I change to ensure custom functions are robust, performant, and seamlessly integrated, avoiding these last-minute production fires?
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.