This repository was archived by the owner on Feb 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 232
v3.27.0 cherry pick from private #2204
Merged
Merged
Conversation
This file contains hidden or 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
(cherry picked from commit d33bf48)
…2338) * This adds in support to the lattice UI application to use the SQL3 endpoint. If the `/sql` endpoint returns 404, it will use the SQL1 endpoint. If the `/sql` endpoint is available, it will send SQL queries to that. It does not try the SQL1 endpoint if the SQL3 endpoint returns an error processing the query. That is, it is all SQL3 or SQL1. - Below are the specific changes: - Adds a file that contains functions for interacting with http services as opposed to just grpc/event-based services. As of this commit, it is only the SQL3 endpoint. - This adds a variable to track if we are using the SQL3 endpoint or not - This adds a function to handle the response from the SQL3 endpoint - Adds a function to eventServices to query the sql3 HTTP endpoint - Fixed a missing semicolon in grpcServices Co-authored-by: Fletcher Haynes <fletcher.haynes@generalassemb.ly> (cherry picked from commit 7ab453e)
substring(string, startIndex,length). (cherry picked from commit aa2a62f)
* Fb:1787 - Clean up * fb-1787 : String upper function * Formatting the files (cherry picked from commit 57ce7c4)
* Move batch.Importer interface to pilosa.Importer In addition to moving the interface, it updates all the methods to use dax.TableID (for example) intead of a string pilosa index name. * Change unused onPremImporter methods to no-op. onPremImporter is a wrapper around API which implements the Importer interface. This is currently only used by sql3 running locally in standard (i.e not "serverless") mode. Because sql3 always sets `useShardTransactionalEndpoint = true`, There are several methods which this implemtation of the Importer interface does not use, and therefore they intentionally no-op. (cherry picked from commit 12d608c)
) This commit introduces an interface called `TableKeyer` which anything that means to represent a "table" can implement. Examples are `dax.QualifiedTable`, `dax.Table`, and `string` (for legacy pilosa calls where Execute simply took `index string`). In the case of `orchestrator.Execute()` and `qualifiedOrchestrator.Execute()`, we are intentionally strict about which type of `TableKeyer` the respective method accepts. If we find, in the future, this is too restrictive, we can loosen that; but for now it helps us understand what is expected. (cherry picked from commit a61d1a9)
(cherry picked from commit 9548e71)
* Fix "qualifer" misspellings * Remove `track_existence` and `shard_width` from SHOW TABLES output * Thread Owner, UpdatedAt, UpdatedBy through SchemaAPI I took the liberty of renaming "LastUpdatedUser" to "UpdateBy" to align with "UpdatedAt". (cherry picked from commit 63cfdb5)
* Make interfaces more specific than "MDS" - Introduce `dax.Schemar` interface - Introduce `dax.Noder` interface - The rest is generally to standardize on the new interfaces. - Remove `pilosa.SchemaInfoAPI` interface - Move `TranslateNode` and `ComputeNode` types from controller to dax package - Remove `queryer.FeatureBaseImporter` - Remove `queryer.MDS` interface - Remove `queryer.Importer` interface - Identify types using an "MDS" interface and split into Noder/Schemar as necessary - Changed `Queryer.orchestrator` to a `map[qual]*qualifiedOrchestrator` because we can't share an orchestrator across quals * Convert orchestrator to use TableKeyer (cherry picked from commit 14f1930)
* fb-1802 : Trim functionality rebase * fb-1802 : trim - updated as per review (cherry picked from commit ac3ffac)
Embeded dataframe-csv-loader command as featurebase subservice (cherry picked from commit f2a13c8)
) (cherry picked from commit e572c8f)
(cherry picked from commit 2146f40)
* Prevent file corruption when writing tar backup to stdout FB-1794 Tar backups written to stdout were coming out corrupt. This turned out to be due to log messages getting written to stdout and ending up in the tar file. We now check to see if the tar file and the log are both going to stdout, and if they are, send the logs to stderr instead. Testing did not have any kind of consistency or validity check. We now compare a tar file sent to a file and a tar file sent to stdout to make sure they're the same. This does not guarantee correctness but does at least catch this form of corruption. * trying different index name Co-authored-by: tgruben <tgruben@gmail.com> Co-authored-by: Todd Gruben <todd@molecula.com> (cherry picked from commit a8996a1)
* Implemented SQL3 LOWER() (cherry picked from commit 4773aab)
(cherry picked from commit eca3168)
(cherry picked from commit 9759602)
(cherry picked from commit c1dbc48)
(cherry picked from commit a4f18fb)
(cherry picked from commit 690a937)
(cherry picked from commit 35c472a)
(cherry picked from commit dbb6d53)
- check that serverlessStorage is not nil before closing it - check that we don't already hold a lock on a serverless storage Manager before trying to load it. This fixed at least one test failure. (cherry picked from commit 87d1c31)
changed empty snapshots/writelogs to return nil which was causing NPE (cherry picked from commit bee666c)
* distribute bulk insert to owning node (cherry picked from commit e8505d8)
…_time (#2394) * Change JSON response name from exec_time to execution-time Execution time stopped working in the CLI because it uses the latest json tag. * Wait, don't break the interface. * Add a test for the sql response json tags. This is to make sure that if someone like Travis just goes and changes a tag name to be more consistent, that we perhaps catch that before it gets to the end user. * Change exec_time to execution-time after all (cherry picked from commit b5dd3ea)
* check root operator after optimize * round of bug fixes (cherry picked from commit 9f04221)
added space_used columns to show tables and fb_cluster_nodes (cherry picked from commit 164aac5)
* adding more error handling for rbf Co-authored-by: Jacob Brinlee <jacobbrinlee@Jacobs-MBP.attlocal.net> (cherry picked from commit c9ce26c)
…8) (#2398) * handle insert into timequantum fields with default 'now' time * allocate on the stack (cherry picked from commit 18fe6a3)
FB-1861 (cherry picked from commit da74f0a)
(cherry picked from commit 4750c22)
Co-authored-by: Julio <julio.martinez@featurebase.com> (cherry picked from commit 581a4d1)
…(#2402) Co-authored-by: Julio <julio.martinez@featurebase.com> (cherry picked from commit 3f91cc3)
* FB-1814: Implement ASCII() (cherry picked from commit f590227)
* handle sum aggregates with ints; handle escaped quotes in blob literals * added test ceoverage * skip subquery test for dax (cherry picked from commit af475a2)
Co-authored-by: Kord Campbell <kord@Bob.local> Co-authored-by: Fletcher Haynes <fletcher@capitalprawn.com> (cherry picked from commit 17cb2cb)
|
Kord Campbell seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
e4b00a2 to
033dd72
Compare
033dd72 to
475bf58
Compare
|
SonarCloud Quality Gate failed.
|
ch7ck
approved these changes
Jan 12, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.








This is (hopefully) the last release before we merge repos. 🚀