Skip to content

Conversation

@erizocosmico
Copy link
Contributor

@erizocosmico erizocosmico commented Jun 14, 2018

Closes #253

We should be able to release a version with indexes after this.

@erizocosmico erizocosmico requested a review from ajnavarro June 14, 2018 12:45
@ajnavarro
Copy link
Contributor

Appears that is out of date with master, can you rebase it?

mcarmonaa and others added 17 commits June 14, 2018 14:48
Signed-off-by: Manuel Carmona <manu.carmona90@gmail.com>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
This PR adds support for unpacked objects, which made the index contain different objects and not match the result of the query without indexes.
A bunch of integration tests for indexes of all tables testing they output the exact same thing as the same query without indexes have been added as well.

Because it's super important to ensure the index is closed so it can be released, each index iterator has now a call to `closeIndexOnError`, which closes the index if there is an error or EOF in an iterator, ensure it's *always* closed.

Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
@erizocosmico
Copy link
Contributor Author

Done

Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
@ajnavarro
Copy link
Contributor

@erizocosmico LGTM

Copy link
Contributor

@ajnavarro ajnavarro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having this issue trying to start gitbase: FATA[0000] unable to start database server error="lstat /home/__/gopkg-index/commit_blobs: no such file or directory"

the name of the error path (the table name) changes on each start retry.

@erizocosmico
Copy link
Contributor Author

That's weird, let me investigate

@erizocosmico
Copy link
Contributor Author

Upgraded go-mysql-server with the fixes for the issues you mentioned

@erizocosmico
Copy link
Contributor Author

Updated go-mysql-server with DROP INDEX statement

@ajnavarro
Copy link
Contributor

@erizocosmico there is something missing from go-mysql-server or can we upload it to latest master version?

@ajnavarro
Copy link
Contributor

I think this is missed: src-d/go-mysql-server#223

@erizocosmico
Copy link
Contributor Author

Yes, that was missing, I'll update that

Signed-off-by: Miguel Molina <miguel@erizocosmi.co>
@ajnavarro ajnavarro merged commit 95b65f8 into master Jun 18, 2018
@ajnavarro ajnavarro deleted the feature/indexable branch June 18, 2018 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants