Skip to content

Releases: oracle-devrel/askdata

release 1.0.0

26 Sep 18:41
@JBAnderson5 JBAnderson5
v1.0.0
dedeed2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
release 1.0.0 Latest
Latest

Release Notes: Oracle AskData

Version: 1.0.0
Release Date: September 26, 2025

Introduction

This document provides the release notes for version 1.0.0 of Oracle AskData. This is the first general availability (GA) release, establishing the foundational feature set for natural language data interaction, query certification, and automated LLM learning.

What's New (New Features)

This release includes the following new features, which are now Generally Available (GA):

  • [cite_start]FEAT-001: Natural Language Querying Engine: The core engine that translates user questions in plain language into executable SQL queries[cite: 1].
  • [cite_start]FEAT-002: Digital Assistant UI: The primary conversational user interface for business users to ask questions[cite: 1].
  • [cite_start]FEAT-003: Trust Harness UI: A dedicated interface for expert users to review, edit, and certify AI-generated queries[cite: 1].
  • [cite_start]FEAT-004: Trust Framework Services: The backend services that manage the trust library, metadata, and query logs to ensure data governance[cite: 1].
  • [cite_start]FEAT-005: Data Source Connectivity: Securely connects to customer data sources using OCI Vault and instance principals[cite: 1].
  • [cite_start]FEAT-006: Caching Layer: Utilizes OCI Cache (Redis) to store results from frequent queries, improving performance[cite: 1].
  • [cite_start]FEAT-007: LLM Integration: Leverages a Llama 3.3 70B model as the core for natural language understanding and SQL generation[cite: 1].
  • [cite_start]FEAT-008: Automated Query Certification: An automated process that certifies new queries by matching them against a library of trusted templates[cite: 1].
  • [cite_start]FEAT-010: Dynamic LLM Instruction Injection: Allows the LLM to learn from expert corrections by dynamically injecting those changes back into the model's prompts[cite: 1].
  • [cite_start]FEAT-011: Performance Logging: A non-functional requirement to log performance metrics and latencies for key user actions has been implemented[cite: 1].
  • [cite_start]FEAT-015: UAT / Demo Environment: A dedicated environment for User Acceptance Testing and internal demos has been established[cite: 1].

Enhancements

The following enhancements have been completed and are now Generally Available (GA):

  • [cite_start]ENH-003: Create Official Deployments: AskData can now be deployed to customer-facing platforms like Devrel and LiveLabs[cite: 1].
  • [cite_start]ENH-004: Internal SME Deployment: Team SMEs can deploy the application to their own internal departments for internal testing and feedback[cite: 1].

Bug Fixes

The following bugs have been resolved in this release and are now considered Generally Available (GA):

  • [cite_start]BUG-002: Duplicate Prompts in Cert Queue: Resolved an issue where duplicate untrusted prompts could accumulate in the certification queue[cite: 1].
  • [cite_start]BUG-003: "Thumbs Down" Creates Duplicates: Fixed a bug where giving a "thumbs down" to a query could create a duplicate entry in the Trust Library instead of deprecating the original[cite: 1].
  • [cite_start]BUG-004: Use Vault and Instance Principals: The engine code has been updated to use OCI Vault and instance principals for secure access[cite: 1].
  • [cite_start]BUG-005: NULL Values Displayed in UI: Fixed an issue where NULL values were displayed in the UI even when the underlying query returned data[cite: 1].

Known Issues

The following issues are known to exist in this version and are being actively worked on:

  • [cite_start]BUG-001: Engine Fails with Empty Trust Library: The NL2SQL engine breaks if the Trust Library is empty[cite: 1]. (Status: In Development)
  • [cite_start]BUG-006: Negative Values Skipped in SUM: Negative values are being skipped during SUM aggregations in the query engine[cite: 1]. (Status: In Definition)
  • [cite_start]BUG-007: Trust Library Requires Manual Seeding: The trust-side application requires the trust library to be manually seeded with an entry[cite: 1]. (Status: Prototyping)
  • [cite_start]BUG-008: Demo Environment Configuration Drift: The demo environment's API GW configuration must be normalized to match the customer environment[cite: 1]. (Status: Prototyping)
  • [cite_start]BUG-009: Unnecessary Fine-Tune Values in Trust Config: The trust_config.json file contains legacy fine-tuning values that should be removed[cite: 1]. (Status: Prototyping)
  • [cite_start]BUG-010: Hardcoded Metric Date in Trust Config: The metric date in trust_config.json is a static value and should be mapped dynamically[cite: 1]. (Status: Prototyping)
  • [cite_start]BUG-011: Missing Engine IP in Trust Config: A deployment failure can occur if the engine's IP for the /get_sql service is not configured in trust_config.json[cite: 1]. (Status: Prototyping)
  • [cite_start]BUG-012: Missing Engine IP in API GW Ingress: A deployment failure can occur if the engine's port 8001 is not added to the API Gateway's ingress list[cite: 1]. (Status: Prototyping)
  • [cite_start]BUG-013: Expose SQL Parse Check as a Service: The engine's SQL parse check should be exposed as a service to simplify the trust-side implementation[cite: 1]. (Status: Prototyping)
Assets 11
Loading