How to skip mybatis method lookup when extends MybatisMapper

Mybatis mapper:

@Mapper
public interface SysUserMapper {
    @Transactional(readOnly = true)
    List<SysUserFullNamePj> selectFullName();

    @Transactional(readOnly = true)
    List<SysUser> selectAll();
}

Spring Data JDBC:

@Repository
public interface SysUserRepo extends PagingAndSortingRepository<SysUser, Long>, SysUserMapper {
    Optional<SysUser> findFirstByUsernameEqualsIgnoreCase(String username);
}

Caused by: org.springframework.data.mapping.PropertyReferenceException: No property 'selectAll' found for type 'SysUser'

Example:

@EnableJdbcRepositories(excludeNamedQueriesStartWith = "select")

@EnableJdbcRepositories(mybatisMethodPrefix = "select")

Use the @EnableJdbcRepositories examples and the PropertyReferenceException as entry points; inspect how methods inherited from SysUserMapper are considered during repository query derivation. Done means a repository can extend both interfaces without treating selectAll and selectFullName as derived Spring Data JDBC queries, with the supplied configuration behavior covered by a test.