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

Why bloomIndex didn't work in workers for filtering stripes #325

Open
hfsugar opened this issue Mar 21, 2022 · 0 comments
Open

Why bloomIndex didn't work in workers for filtering stripes #325

hfsugar opened this issue Mar 21, 2022 · 0 comments

Comments

@hfsugar
Copy link
Contributor

hfsugar commented Mar 21, 2022

Software Environment:

Describe the current behavior

BloomIndex cannot filter stripes in workers.
As shown below, in AbstractOrcRecordReader.filterStripeUsingIndex(), bloomIndex throws IndexLookUpException, this method always return false, which means no need to filter the stripe.
wecom-temp-fa44bec73d7e30e457d3dd5d7aaf8b96

Describe the expected behavior

wecom-temp-8cdb1d67460a5a734daf60ed11f56b82

BloomIndex is used on workers for filtering stripes when reading orc files.

Steps to reproduce the issue

  1. create index idx using bloom on hive.hindex.users (id);
  2. select name from hive.hindex.users where id=123
  3. debug AbstractOrcRecordReader.filterStripeUsingIndex() always returns false.

Related log/screenshots

Special notes for this issue

I think bloom/bitmap/minMax Index created before can be used in workers for filtering stripes/rows by using lookup/matches, but now only bitmapIndex works.

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

No branches or pull requests

1 participant