[VL] Adding configurations for Velox hash join bloom filter feature

[zhouyuan]

Description

Velox recently add the bloom filter when doing hash probe:
facebookincubator/velox#15752

  /// Whether hash probe can generate any dynamic filter (including Bloom
  /// filter) and push down to upstream operators.
  static constexpr const char* kHashProbeDynamicFilterPushdownEnabled =
      "hash_probe_dynamic_filter_pushdown_enabled";

  /// The maximum byte size of Bloom filter that can be generated from hash
  /// probe.  When set to 0, no Bloom filter will be generated.  To achieve
  /// optimal performance, this should not be too larger than the CPU cache size
  /// on the host.
  static constexpr const char* kHashProbeBloomFilterPushdownMaxSize =
      "hash_probe_bloom_filter_pushdown_max_size";

Gluten should add these two necessary configurations for Velox backend

Gluten version

None

[ItsZetty]

@zhouyuan
Hi, if this issue is still open, may I work on it?

[Yohahaha]

we already support specify the value with spark.gluten.sql.columnar.backend.velox.hash_probe_dynamic_filter_pushdown_enabled=true

[FelixYBW]

we already support specify the value with spark.gluten.sql.columnar.backend.velox.hash_probe_dynamic_filter_pushdown_enabled=true

correct, it's spark.gluten.sql.columnar.backend.velox.hashProbe.dynamicFilterPushdown.enabled, enabled by default