Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Create/Drop a single/composite index for relationships #948

Merged
merged 3 commits into from
Jul 13, 2023

Conversation

iamyuchen
Copy link

Since neo4j supports relationship index in versions above 4.x , it is necessary to distinguish node and relationship index in IndexType.

@iamyuchen
Copy link
Author

@meistermeier Hi Gerrit Meier, can you help me to look at this PR, and release a 3.2.40 version?

@meistermeier
Copy link
Collaborator

Thanks for the PR. I have seen this already and it's definitely on my list.
Will have a deeper look within this week.

@meistermeier
Copy link
Collaborator

Sorry for the delay. I have still not found the time to have a more detailed look.
There are other things currently on my desk and I hope to manage getting your PR reviewed next week.

Copy link
Collaborator

@meistermeier meistermeier left a comment

Choose a reason for hiding this comment

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

Thanks for the PR (again). I think that we can adapt this, if you change some minor bits.
FYI: We discarded the whole index functionality with Neo4j-OGM 4.0

You also need to sign CLA, so we can merge your code. https://neo4j.com/developer/cla/

@iamyuchen
Copy link
Author

Thanks for the PR (again). I think that we can adapt this, if you change some minor bits. FYI: We discarded the whole index functionality with Neo4j-OGM 4.0

You also need to sign CLA, so we can merge your code. https://neo4j.com/developer/cla/

Thanks for your review, I have modified the code following the points you mentioned,please check it.
By the way, I have signed CLA.

@@ -287,7 +299,9 @@ private static Set<AutoIndex> initialiseAutoIndex(MetaData metaData) {

for (FieldInfo fieldInfo : getIndexFields(classInfo)) {

IndexType type = fieldInfo.isConstraint() ? IndexType.UNIQUE_CONSTRAINT : IndexType.SINGLE_INDEX;
IndexType type = fieldInfo.isConstraint() ?
Copy link
Collaborator

Choose a reason for hiding this comment

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

Sorry, I missed this bit for the ternary operation clean up. Would be good that it gets the same format as the one, you just fixed.

Copy link
Author

Choose a reason for hiding this comment

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

Thanks, It's my carelessness. I have fixed it.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Happens to be all the time 😄

Copy link
Author

Choose a reason for hiding this comment

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

so could you merge this PR now?

@meistermeier meistermeier self-assigned this Jul 13, 2023
@meistermeier meistermeier merged commit 62909e9 into neo4j:3.2.x Jul 13, 2023
@meistermeier
Copy link
Collaborator

Done, thanks again.

@meistermeier
Copy link
Collaborator

Released with 3.2.41: https://github.com/neo4j/neo4j-ogm/releases/tag/v3.2.41

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.

2 participants