Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Q] <title>adding records from EF to Clickhouse, causing error when async_insert = 1 and wait_for_async_insert = 1 switched on the server #537

Open
Skyhikeeper opened this issue Oct 29, 2024 · 1 comment
Labels
question This issue is a question

Comments

@Skyhikeeper
Copy link

Question

Why would I get the following error on the clickhouse DB when inserting records in the db when teh 2 options are switched on to allow for the db to cache the inerts.

AsynchronousInsertQueue: Failed parsing for query 'INSERT INTO xxxxxx.Sighting (DataWarehouseSightingId, ActionTaken, Colour, Comments, Date, FullImageIsAvailable, FullImageIsThumb, HitStatus, Id, ImageConfigurationId, IsVerified, Latitude, Longitude, Make, Model, PlateImageIsAvailable, ReceivedDate, SightingDate, SightingNoActionReason, SiteLocation, SiteName, SubjectType, SubjectValue, VerifiedValue) FORMAT Values' with query id a6d1efc3-aece-43b0-b77c-54b268ad1764. DB::Exception: Substitution p0 is not set

some data redacted, when the 2 switches are off the system adds but not at high performance

Regards
Terence

@Skyhikeeper Skyhikeeper added the question This issue is a question label Oct 29, 2024
@DarkWanderer
Copy link
Owner

DarkWanderer commented Nov 7, 2024

Hi Terence,

Does the same error appear if both options are off? I assume that if you have wait_for_async_insert=0 then you may just not see the error because the server returns 200 straight away and doesn't wait until results

Edit: realised I haven't read this issue fully - this question has already been answered

Do you by chance have a minimal reproducible example - a piece of code with a small table and single insert? If the difference in behavior is only triggered by flags, I would say it may be an upstream issue (issue in ClickHouse itself), but it's worth looking deeper

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This issue is a question
Projects
None yet
Development

No branches or pull requests

2 participants