Create RecordBatch with num_rows option to avoid bhj error caused by empty output_schema

[wForget]

Which issue does this PR close?

Closes #682

Rationale for this change

Native schema of BroadcastJoin cannot be empty.

https://github.com/kwai/blaze/blob/b662097e7379c4a5912706d58562658b02274335/native-engine/datafusion-ext-plans/src/joins/bhj/full_join.rs#L126

Are there any user-facing changes?

[richox]

thank you for reporting this bug, we can fix it by specifying the number of batch in the code:
https://github.com/kwai/blaze/blob/b662097e7379c4a5912706d58562658b02274335/native-engine/datafusion-ext-plans/src/joins/join_hash_map.rs#L375
replace RecordBatch::try_new with RecordBatch::try_new_with_option

so we don't need to fallback this operator.

[wForget]

thank you for reporting this bug, we can fix it by specifying the number of batch in the code:

https://github.com/kwai/blaze/blob/b662097e7379c4a5912706d58562658b02274335/native-engine/datafusion-ext-plans/src/joins/join_hash_map.rs#L375

replace RecordBatch::try_new with RecordBatch::try_new_with_option
so we don't need to fallback this operator.

Creating a new RecordBatch with option does not seem to solve this isssue, the columns will be empty due to the schema fields being used as projection.

Sorry, I noticed that RecordBatch seems to allow columns to be empty, I will try to do that.