-
Unique key detector tool
What's your use case? More than often, you have to deal with a dataset without knowing what's make a row unique. This can lead to misinterpret the data, cartesian product at join and other funny stuff. What's your proposed solution? This is a feature I haven't seen in any data prepation/etl. The core feature is to detect…
-
ADBC connectivity : faster columnar storage query
Hello all, ADBC is a database connection standard (like ODBC or JDBC) but specifically designed for columnar storage (so database like DuckDB, Clickhouse, MonetDB, Vertica...). This is typically the kind of stuff that can make Dataiku way faster. more info in https://arrow.apache.org/blog/2023/01/05/introducing-arrow-adbc/…
-
Convert Visual and Structured Visual Agent to Agent Code
Hello, Visual and Structured Visual Agents are easy to design, a lot easier than an agent code. However, it creates a lot of dependancy to Dataiku, meaning some restrictions to use them. On the other side, a pure code agent is pretty hard to desig but it brings some freedom. I tried to convert a SV agent to code agent,…
-
Dataiku Headless: Add Support for SSO Authentication
As industry moves towards passwordless, this is a request to provide support for SSO-based authentication for Dataiku Headless (OAuth Authorization Code flow with PKCE), as an alternative to requiring users to manually create, configure and manage a Dataiku API keys. Users should be able to authenticate interactively…
-
Feature Request: Dataiku CoBuild - Cost Analysis
Provide cost visibility and reporting by project, in addition to the existing user-level usage oversight (/admin/ai-services/usage/), allowing administration teams and platform stakeholders to understand where CoBuild usage and associated costs are coming from. This should include a breakdown or summary of the activity…
-
Feature Request: Dataiku CoBuild "Auto Mode"
As costs become more of a priority, it would be useful to have an “Auto Mode” for model selection, which automatically selects the most appropriate model for each query to reduce unnecessary token spend. Users should still have the option to manually select a model for an individual query, without changing their default…
-
Improve integration of custom and plugin models in VisualML
The functionality to continuously expand VisualML with plugin models, either from Dataiku or by coding our own plugins is very valuable to us. For example, we use the General Linear Models plugin a lot to support our actuarial team. There are some areas where the integration of such plugins is not yet ideal in VisualML…
-
Feauture Request: Add Export Button on Users and Groups pages (OnPrem Deployment)
Currently, platform administrators can export the user and group authorisation matrix from /admin/security/authorization-matrix/. A similar Export capability is required for the Users (/admin/security/users/) and Groups (/admin/security/groups/) pages. This would provide administrators with a clear overview of existing…
-
Visual ML + Deployed Model Diagnostic Outputs
It would be great to be able to export data related to failed or ignored rows within both the visual ml and deployed model diagnostics with a label denoting the reason for not training. This would keep the user from using other methods to a. locate which rows did not get trained and b. the reason for them not getting…
-
Output Model Exclusions
It would be handy to be able to instead of completely ignore invalid rows in model predictions to have the option to still output them with a potential 'excluded' marker and some diagnostic reason. Currently having to do anti-joins between model outputs and input to figure out which records did not pass adds extra workload…