> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/changelog/2024.md).

# 2024

- [September 6, 2024](https://docs.e6data.com/query-engine/changelog/2024/6th-sept-2024.md): Enhanced Data Analyst role
- [June 6, 2024](https://docs.e6data.com/query-engine/changelog/2024/6th-june-2024.md): Latest update- MFA and service accounts.
- [April 18, 2024](https://docs.e6data.com/query-engine/changelog/2024/18th-april-2024.md): This page covers the latest updates to e6data, including improved connectivity, security, and query editing features.
- [April 9, 2024](https://docs.e6data.com/query-engine/changelog/2024/9th-april-2024.md): This page explains the latest updates to e6data, focusing on schema behavior within the Schema Explorer for improved navigation and management.
- [March 30, 2024](https://docs.e6data.com/query-engine/changelog/2024/30th-march-2024.md): This page covers recent e6data updates, including catalog privileges for column masking and row filtering, query history enhancements, and support for deletion vectors in Iceberg tables.
- [March 16, 2024](https://docs.e6data.com/query-engine/changelog/2024/16th-march-2024.md): This page highlights the new feature for exporting query history to CSV, enhancing data analysis and reporting capabilities on the e6data platform.
- [March 14, 2024](https://docs.e6data.com/query-engine/changelog/2024/14th-march-2024.md): This page covers the latest updates to e6data, including the new DataExport role, improved resource selection in catalog privileges, and the addition of client-perceived time in query history.
- [March 12, 2024](https://docs.e6data.com/query-engine/changelog/2024/12th-march-2024.md): recent e6data updates, including enhanced cluster connection info, improved connectivity, and catalog refresh capabilities for Data Analyst roles.
- [March 2, 2024](https://docs.e6data.com/query-engine/changelog/2024/2nd-march-2024.md): Covers the latest e6data updates, including catalog privileges, support for liquid clustering, new functions, and the impersonation feature for the Metabase BI tool via Apache Ranger.
- [February 10, 2024](https://docs.e6data.com/query-engine/changelog/2024/10th-february-2024.md): This page introduces the new gateway connectivity feature, enabling seamless external client connections through endpoints on the e6data platform.
- [February 3, 2024](https://docs.e6data.com/query-engine/changelog/2024/3rd-february-2024.md): This page covers the new connectivity and notebook features on the e6data platform.
- [January 17, 2024](https://docs.e6data.com/query-engine/changelog/2024/17th-january-2024.md): This page highlights the introduction of new functionalities on the e6data platform.
- [January 9, 2024](https://docs.e6data.com/query-engine/changelog/2024/9th-january-2024.md): This page covers the latest e6data enhancements, including new functionalities, bug fixes, and performance optimizations.
- [January 3, 2024](https://docs.e6data.com/query-engine/changelog/2024/3rd-january-2024.md): This page outlines the platform enhancement and catalog auto-refresh feature


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/changelog/2024.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
