frontend entered unreachable code when creating SINK INTO TABLE
#17278
Comments
BugenZhao
changed the title
SINK INTO TABLE
|
Thanks for your feedback. we will discuss about how to fix later. Before that, you can use |
|
@st1page Let's fix the error message. The panic stack is really scary. |
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I was created a kafka ingestion and also created a table, I tried to create a sink to insert kafka data into this table.
When I try to to run the above query, it gave errors.
Error message/log
To Reproduce
create table bms.kafka.t_member_addition (
member_addition_id bigint,
member_id bigint,
setup_form_id bigint,
setup_form_dtl_id bigint,
addition_answer varchar,
record_status_id smallint,
create_uid varchar,
create_dt timestamptz,
update_uid varchar,
update_dt timestamptz,
primary key (member_addition_id)
)
WITH (
connector='kafka',
topic='t_MEMBER_ADDITION',
properties.bootstrap.server='10.28.6.66:9092',
scan.startup.mode='earliest',
) FORMAT DEBEZIUM ENCODE JSON;
create table bms.public.t_member_addition_info_date (
member_addition_id bigint,
info_date timestamptz default now(),
primary key (member_addition_id)
);
create sink bms.sink.t_member_addition_info_date into bms.public.t_member_addition_info_date
as
select
member_addition_id
from bms.kafka.t_member_addition;
Expected behavior
Success to create sink
How did you deploy RisingWave?
I ran in local Kubernetes Cluster
root@ali-k8u200-1:/home/appadmin# helm repo add risingwavelabs https://risingwavelabs.github.io/helm-charts/ --force-update
"risingwavelabs" has been added to your repositories
root@ali-k8u200-1:/home/appadmin# helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "risingwavelabs" chart repository
Update Complete. ⎈Happy Helming!⎈
root@ali-k8u200-1:/home/appadmin# nano values.yaml
values.yaml
Configure meta store backend.
metaStore:
sqlite:
enabled: true
path: /data/metastore/risingwave.db
Configure state store backend.
stateStore:
localFs:
enabled: true
path: /data/statestore
Enable standalone mode. Mount the PVC to data path.
standalone:
enabled: true
extraVolumeMounts:
mountPath: /data/metastore
subPath: metastore
mountPath: /data/statestore
subPath: statestore
volumeClaimTemplates:
name: data
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 50Gi
root@ali-k8u200-1:/home/appadmin# helm install risingwave risingwavelabs/risingwave --namespace risingwave -f values.yaml
NAME: risingwave
LAST DEPLOYED: Mon Jun 17 12:17:00 2024
NAMESPACE: risingwave
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Welcome to fast and modern stream processing with RisingWave!
Check the running status with the following command:
Try accessing the SQL console with the following command:
Keep the above command running and open a new terminal window to run the following command:
For more advanced applications, refer to our documentation at: https://www.risingwave.dev
root@ali-k8u200-1:/home/appadmin# kubectl get all -n risingwave
NAME READY STATUS RESTARTS AGE
pod/risingwave-standalone-0 1/1 Running 0 3m12s
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/risingwave ClusterIP 10.233.63.123 4567/TCP 3m15s
NAME READY AGE
statefulset.apps/risingwave-standalone 1/1 3m15s
The version of RisingWave
PostgreSQL 13.14.0-RisingWave-1.9.1 (4fa6c8b)
Additional context
No response
The text was updated successfully, but these errors were encountered: