12 Commits
Author SHA1 Message Date
Calvin Kirs 83d300d279 [chore](fe) Remove the standalone auditloader plugin from fe_plugins (#68563)
### What problem does this PR solve?

Issue Number: None

Related PR: None

Problem Summary:

`fe_plugins/auditloader` is the old standalone audit loader plugin,
which had to be built with `build-plugin.sh` and installed with `INSTALL
PLUGIN`. FE now ships a built-in audit loader
(`org.apache.doris.plugin.audit.AuditLoader`), registered by `PluginMgr`
at startup, which writes audit events into `__internal_schema.audit_log`
and is switched by the global variable `enable_audit_plugin`. Nothing in
FE or the build depends on the standalone copy any more, and it has
drifted from the built-in one. This PR removes the module and its entry
in `fe_plugins/pom.xml`.

The legacy `pytest/deploy` scripts had an optional path that installed
this plugin. When `output/audit_loader/auditloader.zip` existed, they
rendered `plugin_auditload.conf`, unpacked the zip into the FE
directory, created `doris_audit_db__.doris_audit_tbl__` and ran `INSTALL
PLUGIN`. No build produces that zip, so the path never ran. This PR
removes that path, `plugin_auditload.conf`, and the `deploy_audit`
parameter it threaded through `prepare_palo_package()` and
`start_palo()`.
2026-09-29 09:58:12 +08:00
Arpit Jain 8f65b7ccb4 [fix](build) Update pytest dependency pins for security advisories (#63188)
Problem Summary:
`pytest/requirements.txt` currently pins several dependencies to
vulnerable versions flagged by Dependabot. This PR updates the pinned
versions for `certifi`, `idna`, `PyMySQL`, `requests`, and `urllib3` to
patched releases so the pytest tooling dependencies are no longer on
known vulnerable ranges.


Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
2026-07-10 16:46:38 +08:00
zclllyybb 10704d7b3f [refactor](runtime-filter) remove bitmap runtime filter (#64314)
Remove the obsolete bitmap runtime filter planning and execution path
while preserving thrift compatibility entries as Deprecated.

Root cause:
BITMAP_FILTER still had a dedicated FE planning branch for
bitmap-containing nested-loop join predicates and matching BE
runtime/filter predicate implementations. Even though the path is no
longer intended to be planned, helper objects and runtime mappings kept
it reachable.

Fix:
- Keep existing thrift ids and fields for BITMAP_PRED,
TRuntimeFilterType.BITMAP, bitmap_target_expr, bitmap_filter_not_in, and
is_output_left_side_only, but mark them Deprecated.
- Remove FE bitmap runtime-filter generation, pushdown, translation,
session-variable acceptance, and nested-loop join probe-only special
handling.
- Delete VBitmapPredicate, BitmapFilterFunc, and bitmap column predicate
execution objects.
- Adjust runtime-filter tests and regressions to verify bitmap runtime
filters are not planned.
2026-06-11 14:22:15 +08:00
Refrain 81b2d2bde5 [remove](sync JOB) Remove the code about SYNC JOB (#58008)
now we do not support the SYNC JOB feature, so remove the code from
kernel.
2025-11-18 09:43:20 +08:00
Gabriel 0c1570769e [minor](conf) Deprecate variable PARALLEL_FRAGMENT_EXEC_INSTANCE_NUM (#46173) 2025-01-09 11:31:33 +08:00
Pxl abeaafee8f [Chore](function) remove repeat max num (#37907)
## Proposed changes
remove repeat max num
2024-07-18 16:00:09 +08:00
Pxl e58fcf0f7a [Feature](column) do not change column nullable on ColumnDef (#35574)
do not change column nullable on ColumnDef

1. bitmap/hll/quantile_state will directly change nullable to false
1. Currently, complex types do not support nullable in the storage
layer. If it is set to null, it should be coredump.
2. It is meaningless to set complex types to null. For example, bitmap
can use bitmap_empty to represent null to avoid nullable overhead.
3. Users reported that if it is a not null bitmap. When inserting into,
it is necessary to explicitly declare bitmap_empty, which is
troublesome. However, the work of supporting the default value of
bitmap_empty for complex columns has been claimed by the community.
https://github.com/apache/doris/issues/34228
4. Consider changing it here so that if null is explicitly specified
when creating a table, an error will be reported. If it is not
explicitly specified (the default will be null), it is not null.
2. The aggregate type REPLACE_IF_NOT_NULL will directly change nullable
to true
1. If it is a not null column, using REPLACE_IF_NOT_NULL is meaningless,
which is equivalent to REPLACE.
2. Consider changing it here so that if not nullable is encountered, an
error will be reported, and a prompt to use REPLACE will be given.
2024-05-30 14:29:14 +08:00
zhiqiang 524bce3c07 [doc](auditlog) update description of field sql_digest (#28340) 2023-12-13 19:27:48 +08:00
zhiqiang 0931eb536c Revert "[Improvement](auditlog) add column catalog for audit log and audit log table (#26403)" (#28177)
This reverts commit daea751a98.
2023-12-08 18:46:59 +08:00
zhangy5 d1e163126c [regression] remove useless case (#27590) 2023-11-28 10:39:55 +08:00
Yulei-Yang daea751a98 [Improvement](auditlog) add column catalog for audit log and audit log table (#26403) 2023-11-08 10:25:15 +08:00
zhangy5 3e0933a507 [Enhancement] submit Baidu test cases (#22883) 2023-09-15 11:56:08 +08:00