Bump v0.3.4+ dev #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Joy Arulraj <[email protected]> Co-authored-by: Joy Arulraj <[email protected]>
1. Fix all BUILD warning. 2. Fix all links. 3. Add circle ci test for Doc build and link validation. Documentation content updates will be in the following PRs. --------- Co-authored-by: Gaurav Tarlok Kakkar <[email protected]> Co-authored-by: Joy Arulraj <[email protected]> Co-authored-by: Joy Arulraj <[email protected]>
Co-authored-by: Jiashen Cao <[email protected]>
Cannot reproduce the bug but added robust testcases. #1149 The inconsistent behavior might be happening because of another bug where we were creating a table even if the select query failed. We have fixed that, so it may fix this bug as well.
Added support for Pinecone in EvaDB. Since pinecone requires an API key, created an evironment variable in evadb yml file. If not set, we check the os environment.
I will need some feedback on the design here. @xzdandy @gaurav274 This PR reflects my initial design for in-database index features like pgvector. My initial idea is to offload as much as possible to the native database. When we create an index and do the index scan, we simply push an emulated query to the underlying database. While this is doable, this will introduce separate implementation paths in different components including the optimizer and the executor. Other than the current design, another option is to reuse the third-party vector integration interface. There are also a few details that I am not clear about * For other vector libraries, we keep an index entry in our own catalog. Do we still maintain that even for pgvector? In the original implementation, the index catalog entry is linked to a table catalog entry. Because in this case, the table is inside Postgres, we also need to change the implementation here a little bit. * ~~(Issue related to performance). Following the current create index implementation, data will be fetched from Postgres first but it is not really needed. The create index will anyway run inside Postgres.~~ * ~~The current vector index scan is implemented based on `_row_id`. When it is scanning data from Postgres, we need to figure out a way to populate `_row_id` for the native database engine.~~
* Roll back my previous changes. The previous code is correct. The release URL is not updated until we upload assets, so it should affect things. * The root cause is the checkout action used by github tries to optimize and does not pull histories of commits besides the head. Consequently, our script cannot get changelog from the git histories.
fixes warnings received when using superagi. fixes issue #1127
The integration test currently fails if pinecone is not installed. Added a skip marker for the same.
This PR introduces a colab notebook that showcases the usage of Ludwig-based predictive analysis in EvaDB. --------- Co-authored-by: Gaurav Tarlok Kakkar <[email protected]>
Co-authored-by: Andy Xu <[email protected]>
Starting this PR for integrating sklearn linear regression for EvaDb. --------- Co-authored-by: Jineet Desai <[email protected]>
Added support for ChromaDB in Eva. Will focus on benchmarking the existing vector stores after this.
Added - Parser for SET statement - Class for SET statement - StatementType.SET to parser.types
* Drop index has some bugs on newly added indexes * Improve msg * Enhance test cases
Bumps [sphinxcontrib-youtube](https://github.com/sphinx-contrib/youtube) from 1.2.0 to 1.4.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sphinx-contrib/youtube/releases">sphinxcontrib-youtube's releases</a>.</em></p> <blockquote> <h2>v1.4.1</h2> <ul> <li>Correct the Sphinx version dependency.</li> </ul> <h2>v1.4.0</h2> <ul> <li>Add support for PeerTube</li> <li>Various minor big fixes</li> </ul> <h2>v1.3.0</h2> <ul> <li>Code and documentation refactor</li> <li>Contributing instructions</li> <li>Installation and configuration instructions</li> <li>Only download thumbnails for LaTeX targets.</li> <li>Fix to thumnail folder name.</li> <li>parallel build safety.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sphinx-contrib/youtube/commit/fff4ab29a8606676fe5d64850a2f50114d8be3eb"><code>fff4ab2</code></a> point release to correct Sphinx dependency</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/43ba3ca55815833e90a8f59b24a0b581314c3524"><code>43ba3ca</code></a> Release 1.4 (<a href="https://redirect.github.com/sphinx-contrib/youtube/issues/62">#62</a>)</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/8dfbf08f173acafe6b1997321d57e00eb5174103"><code>8dfbf08</code></a> Add peertube support (<a href="https://redirect.github.com/sphinx-contrib/youtube/issues/59">#59</a>)</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/976d223dbefe550db68a11523a13e61f9e33947c"><code>976d223</code></a> don't use status_iterator alias</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/c8dda2494c824b83f10b5248548f556d7d65a428"><code>c8dda24</code></a> drop Python 3.7 from CI</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/77783fc910d76d468554f545ddc5b7f74321a1b6"><code>77783fc</code></a> fix: use correct url when using privacy mode (<a href="https://redirect.github.com/sphinx-contrib/youtube/issues/58">#58</a>)</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/4ffb53901890f94a69e34a4809e5cea2b041b8e1"><code>4ffb539</code></a> not epub</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/6dd8da0b1250b5c76cb00c4f7d9670fdfa8cc4e3"><code>6dd8da0</code></a> force readthedocs</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/919a1a8b50607017752a0994baabf72474847905"><code>919a1a8</code></a> bump version</li> <li><a href="https://github.com/sphinx-contrib/youtube/commit/d5c04a406eb841270f3a95e72f4d3c4a679e305a"><code>d5c04a4</code></a> Updated installation, configuration and usage information. (<a href="https://redirect.github.com/sphinx-contrib/youtube/issues/54">#54</a>)</li> <li>Additional commits viewable in <a href="https://github.com/sphinx-contrib/youtube/compare/v1.2.0...v1.4.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Relates to: #999 #960 - [x] Skip the [17-home-rental-prediction.ipynb](https://github.com/georgia-tech-db/evadb/blob/staging/tutorials/17-home-rental-prediction.ipynb) which does not run on Circle CI due to Postgres setup. - [x] Fix the format issue in current documentation pages - [x] Add a new usecase documentation page for [17-home-rental-prediction.ipynb](https://github.com/georgia-tech-db/evadb/blob/staging/tutorials/17-home-rental-prediction.ipynb) - [x] Refine the [model training page under AI engines ](https://evadb.readthedocs.io/en/stable/source/reference/ai/model-train.html) to include Ludwig and Sklearn. - [x] Provide a reference table for available configuration parameters for those two AI engines
Add `testmon` in pytest --------- Co-authored-by: xzdandy <[email protected]>
1. `IF NOT EXISTS` support added for native databases. 2. Better error messaging for #1219 --------- Co-authored-by: Jiashen Cao <[email protected]> Co-authored-by: Andy Xu <[email protected]>
- [x] add `time.sleep` in `DummyLLM` to make it run longer for the resue test cases. - [x] always cache even the test is failed. - [x] skip pinecone tests due to free-tier limit.
We need to force refesh .testmondata on staging.
1. `CREATE TABLE` returns better response messages. 2. Skipping `PINECONE` testcase as it is flaky. 3. Handle the scenario when `CREATE TABLE AS SELECT` fails in the native database table.
Reverts #1111 This PR breaks the staging. I will work with @sudoboi to fix and improve the issues we found. Co-authored-by: Abhijith S Raj <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.