Overriding Repository methods exposed them under /search endpoint [DATAREST-920]

Marc Zampetti opened DATAREST-920 and commented

When one overrides methods provided by an inherited Repository interface, such as CrudRepository in order to do things like add @Query parameters or @PreAuthorize information, Spring Data Rest exposes the overridden method under the /search/ endpoint.

This seems like an issue since that changes the signature of the API in an unintendded way. Using @RestResource(exported = false) won't work, as that will deny access to the method.

For example, when overring the findAll() method to add a @Query adjustment, the <repository>/search/findAll method now appears in the output. And calls to <repository>/search/findAll now also work.

It seems like this is unintended behavior, and should be resolved in some manner. I see a couple of ways to do so:

• If the @Override annotation is on the method, don't expose in the /search endpoint. That might not work if the method is coming from another custom interface however.
• Filter out methods that are overrides of known Repository interfaces, maybe by using the package name or some other marker interface.
• Add a hide option to @RestResource that would hide the method from generated metadata, but wouldn't restrict access like exported = false does

No further details from DATAREST-920