Skip to content

Conversation

@xenoterracide
Copy link
Contributor

add autoconfiguration for bolt driver, including tests

gh-6690

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 25, 2016
@snicoll snicoll added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Aug 25, 2016
@snicoll snicoll added this to the 1.4.1 milestone Aug 25, 2016
@vince-bickers
Copy link

should probably also take this opportunity to add support for https as well?

@snicoll
Copy link
Member

snicoll commented Aug 25, 2016

@vince-bickers not in this issue, no. Feel free to create a separate PR for that.

@xenoterracide
Copy link
Contributor Author

let me know if I need to make any changes to the code/commits before they can be merged.

@snicoll snicoll self-assigned this Aug 26, 2016
driverConfiguration.setDriverClassName(BOLT_DRIVER);
driverConfiguration.setURI( DEFAULT_BOLT_URI );
return;
}
Copy link
Member

Choose a reason for hiding this comment

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

That's a breaking in behaviour. If you didn't specify anything and you upgrade, you're using bolt instead of http. I need to better understand the impact of this change before considering the code as is.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

my assumption on this is simply that since spring boot/platform doesn't provide this driver (or the file one) that if you add it manually, you probably want to use it, I'm ok if this isn't auto behavior, that just made sense to me.

@snicoll
Copy link
Member

snicoll commented Aug 26, 2016

I remember why I didn't support bolt in 1.4.0. It is a Neo4j 3.0.0 specific thing and it wasn't available at the time we implemented the feature.

@xenoterracide I am a bit confused. I see no indication in your PR that Spring Boot provides dependency management for the bolt driver. We don't have dependency management for neo4j-java-driver which looks suspicious to me. It isn't used anywhere in the codebase, not even in a sample. What did you add to your own project to use it?

@snicoll snicoll added status: waiting-for-feedback We need additional information before we can continue status: on-hold We can't start working on this issue yet labels Aug 26, 2016
@snicoll snicoll removed this from the 1.4.1 milestone Aug 26, 2016
@snicoll snicoll removed status: on-hold We can't start working on this issue yet status: waiting-for-feedback We need additional information before we can continue labels Aug 26, 2016
@snicoll snicoll added this to the 1.4.1 milestone Aug 26, 2016
@snicoll snicoll closed this in 47c568a Aug 26, 2016
snicoll added a commit that referenced this pull request Aug 26, 2016
* pr/6746:
  Polish contribution
  Detect Neo4j bolt driver
@snicoll
Copy link
Member

snicoll commented Aug 26, 2016

I changed my mind. The bolt URL parsing has been merged in master. Regarding the detection of the bolt driver and the behaviour change, we can't do that in a bug fix release. Feel free to submit another issue for 1.5 but if you do, I'd like to get more details (per my previous comment). Thanks for the PR.

@xenoterracide xenoterracide deleted the neo4j-bolt branch April 8, 2021 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants