![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
haystack-experimental
Advanced tools
The haystack-experimental
package provides Haystack users with access to experimental features without immediately
committing to their official release. The main goal is to gather user feedback and iterate on new features quickly.
For simplicity, every release of haystack-experimental
will ship all the available experiments at that time. To
install the latest experimental features, run:
$ pip install -U haystack-experimental
[!IMPORTANT] The latest version of the experimental package is only tested against the latest version of Haystack. Compatibility with older versions of Haystack is not guaranteed.
Each experimental feature has a default lifespan of 3 months starting from the date of the first non-pre-release build that includes it. Once it reaches the end of its lifespan, the experiment will be either:
Name | Type | Expected End Date | Dependencies | Cookbook | Discussion |
---|---|---|---|---|---|
EvaluationHarness | Evaluation orchestrator | October 2024 | None | Discuss | |
ChatMessageWriter | Memory Component | December 2024 | None | Discuss | |
ChatMessageRetriever | Memory Component | December 2024 | None | Discuss | |
InMemoryChatMessageStore | Memory Store | December 2024 | None | Discuss | |
Auto-Merging Retriever & HierarchicalDocumentSplitter | Document Splitting & Retrieval Technique | December 2024 | None | Discuss | |
LLMMetadataExtractor | Metadata extraction with LLM | December 2024 | None | Discuss | |
AsyncPipeline | Async Pipeline & Components | February 2024 | None | Discuss | |
Pipeline | Pipeline | January 2025 | None | Discuss |
Name | Type | Final release | Cookbook |
---|---|---|---|
ChatMessage refactoring; Tool class; tool support in ChatGenerators; ToolInvoker | Tool Calling support | 0.4.0 |
Name | Type | Final release | Cookbook |
---|---|---|---|
OpenAIFunctionCaller | Function Calling Component | 0.3.0 | None |
OpenAPITool | OpenAPITool component | 0.3.0 | Notebook |
Experimental new features can be imported like any other Haystack integration package:
from haystack.dataclasses import ChatMessage
from haystack_experimental.components.generators import FoobarGenerator
c = FoobarGenerator()
c.run([ChatMessage.from_user("What's an experiment? Be brief.")])
Experiments can also override existing Haystack features. For example, users can opt into an experimental type of
Pipeline
by just changing the usual import:
# from haystack import Pipeline
from haystack_experimental import Pipeline
pipe = Pipeline()
# ...
pipe.run(...)
Some experimental features come with example notebooks and resources that can be found in the examples
folder.
Documentation for haystack-experimental
can be found here.
Experiments should replicate the namespace of the core package. For example, a new generator:
# in haystack_experimental/components/generators/foobar.py
from haystack import component
@component
class FoobarGenerator:
...
When the experiment overrides an existing feature, the new symbol should be created at the same path in the experimental
package. This new symbol will override the original in haystack-ai
: for classes, with a subclass and for bare
functions, with a wrapper. For example:
# in haystack_experiment/src/haystack_experiment/core/pipeline/pipeline.py
from haystack.core.pipeline import Pipeline as HaystackPipeline
class Pipeline(HaystackPipeline):
# Any new experimental method that doesn't exist in the original class
def run_async(self, inputs) -> Dict[str, Dict[str, Any]]:
...
# Existing methods with breaking changes to their signature, like adding a new mandatory param
def to_dict(new_param: str) -> Dict[str, Any]:
# do something with the new parameter
print(new_param)
# call the original method
return super().to_dict()
Direct contributions to haystack-experimental
are not expected, but Haystack maintainers might ask contributors to move pull requests that target the core repository to this repository.
As with the Haystack core package, we rely on anonymous usage statistics to determine the impact and usefulness of the experimental features. For more information on what we collect and how we use the data, as well as instructions to opt-out, please refer to our documentation.
FAQs
Experimental components and features for the Haystack LLM framework.
We found that haystack-experimental demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.