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
WARNING: don't know how to handle filter of type *google_bigtable_v2.RowFilter_RowKeyRegexFilter #567
Comments
Can you possibly send a small test case that inserts a row and then tries unsuccessfully to filter for it using a regex? The code you already provided is close but "test-pattern" doesn't seem like it should match the row key so I think I'm missing something. One thing to note is that the emulator can't handle binary regular expressions. See this document for supported filters and limitations. Also, the error you originally saw was valid until a month or two ago when support for RowKeyRegexFilter was added. |
Yeah I saw the binary regex note. Give me a couple of days, am travelling today. OK about the time it was added. It's not throwing an error at least but might be something else. I'll write a test for it and post the code in a couple. |
Ok, a much reduced function including test. Should filter by the ap_mac in this case. Works OK on production table. Let me know if I've either done something wrong (!) or if you need more information. (format_mac just strips the - from the mac address)
And the test:
Which fails at the last assert. The regexfilter's not being applied using the emulator. |
The fix has been released in gcloud for some time. |
Running some python units tests against the bigtable emulator, I saw the following error in the logs:
I tried a few different regex patterns w/o success (bytes, string etc). My row key looks like this
3917#88DC961302E8#201703
and the regex 'test-patter' ain't working.Works against production table without issue.
I was running Google Cloud SDK 138.0.0 so I updated and am now running this:
The error has now gone from the logs BUT the problem still remains. The filter isn't applying.
The text was updated successfully, but these errors were encountered: