google-cloud-go: bigtable emulator: column_qualifier_regex returns parsing error on invalid Unicode sequences

Hello guys,

As a continuation of #1405 I’m raising following issue when used gcloud components v.257.0.0. (expected to be fixed till 251.0.0) binary characters in column_qualifier_regex still retrun parsing error (only in emulator of google):

[bigtable] 2019/08/12 12:34:20 Bad pattern “Ea\xc6\>R\%\xf1\xd6\C*”: error parsing regexp: invalid UTF-8: ?\>R\%??\C*$

Here the error from postman:

“status”: { “code”: “INVALID_ARGUMENT”, “description”: “Error in field ‘column_qualifier_regex_filter’ : error parsing regexp: invalid UTF-8: \ufffd\\>R\\%\ufffd\ufffd\\C*$”, “cause”: null, “ok”: false }

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 1
Comments: 23 (10 by maintainers)

Most upvoted comments

Great, so we can both confirm that the bug was fixed in source code at least as from months ago!

A successful result shows that something isn’t right in perhaps your deployment of your emulator or that the officially published version wasn’t updated somehow.

I am going to kindly ping @garye to ask that we re-build and re-deploy the Bigtable emulator.

odeke-em on Aug 13, 2019

Hello Valentin, Please just try first running it simply as a normal executable without having to package it in Docker and then run that repro that I provided all on the same machine, without having to run with Postman (am not sure about Postman since that requires using gRPC) – I ask because the simpler the setup, the easier it is to isolate the problem. I’d prefer that we see the differences and I’ve provided binaries for various platforms: Linux, Windows, macOS so that you aren’t restricted to one machine and that anyone can re-run to have a good final result.

chmod +x bemulator_linux && ./bemulator_linux and then BIGTABLE_EMULATOR_HOST=localhost:9000 go run main.go

Is the simple setup is the simple setup, (as I had posted earlier) that you’ll need 😃

On Tue, Aug 13, 2019 at 2:02 AM Valentin Nikolov notifications@github.com wrote:

Hey, @odeke-em https://github.com/odeke-em

Thank you for the binaries! I’m copying and run as command in Dockerfile the bemulator_linux one. I’ve changed all settings in my docker-compose.yml file too to use the new port 9000 (instead of 8086) and finally when run in postman my queries to check the changes I still do not see any difference to be on the error result. Though if you are completely sure the problem is fixed, maybe some double check on the configuration for the main release of gcloud could find the reason still the new parsing problem with the binary characters in column_qualifier_regex? If this is only a configuration error I am fine to wait for next official release where that will be arranged but if all changes are properly configured it seems there are some unhandled cases that need to be fixed.

Best Regards, Valentin

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/googleapis/google-cloud-go/issues/1531?email_source=notifications&email_token=ABFL3V5PU4VYSEBIJRFNZ6LQEJTANA5CNFSM4ILA4ARKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4E345A#issuecomment-520732276, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFL3V3LFM2XTWGGJ7V2HQDQEJTANANCNFSM4ILA4ARA .

odeke-em on Aug 13, 2019