Spring GemFire
  1. Spring GemFire
  2. SGF-247

boolean based repository queries generate UnsupportedOperationException in non PDX serialized entities

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.1, 1.3.2, 1.3.3
    • Fix Version/s: 1.3.3, 1.4 M1 (Dijkstra)
    • Labels:
      None

      Description

      Without using PDX serialization, boolean based queries throw on unsupported operation out of Predicates.getOperator. The type:Type parameter to the method comes in as TRUE or FALSE, however neither of these are supported in the getOperator method.

      I have attached a patch file that I believe corrects the issue completely as well as a test project to replicate the issue.

      Exact error messages are:

      1. Predicates.patch
        1 kB
        Frank Moley
      2. repositoryQueries.xml
        1 kB
        John Blum
      3. RepositoryQueriesTest.java
        4 kB
        John Blum
      4. User.java
        2 kB
        John Blum
      5. UserRepository.java
        1 kB
        John Blum

        Activity

        Hide
        John Blum added a comment -

        Committed and checked into 1.4.0.BUILD-SNAPSHOT

        Committed and checked into 1.3.3.RELEASE

        Show
        John Blum added a comment - Committed and checked into 1.4.0.BUILD-SNAPSHOT Committed and checked into 1.3.3.RELEASE
        Hide
        John Blum added a comment -

        Currently blocked due to permission issues pushing to Maven Central. WIP...

        Show
        John Blum added a comment - Currently blocked due to permission issues pushing to Maven Central. WIP...
        Hide
        John Blum added a comment -

        So, our CI environment includes an Artifactory plugin that enables a successful build with all artifacts to be pushed to Maven Central. This plugin was recently updated by the JFrog team to push to Bintray as well. As it turns out, there are HTTP permission issues pushing to Bintray that block the process and prevent publishing to Maven Central. I have reached out the IT admin group for help addressing this matter and they have forwarded the request to the JFrog team. Currently in waiting. Sorry for the delay.

        Show
        John Blum added a comment - So, our CI environment includes an Artifactory plugin that enables a successful build with all artifacts to be pushed to Maven Central. This plugin was recently updated by the JFrog team to push to Bintray as well. As it turns out, there are HTTP permission issues pushing to Bintray that block the process and prevent publishing to Maven Central. I have reached out the IT admin group for help addressing this matter and they have forwarded the request to the JFrog team. Currently in waiting. Sorry for the delay.
        Hide
        John Blum added a comment -

        Apparently, the new 1.3.3.RELEASE artifacts did get pushed to Bintray and Maven Central properly despite the re-occurring error in our CI environment Artifactory build plugin that pushed the artifacts to Bintray and Maven Central respectively. If there are problems, please let us know by re-opening this ticket. Thanks.

        Show
        John Blum added a comment - Apparently, the new 1.3.3.RELEASE artifacts did get pushed to Bintray and Maven Central properly despite the re-occurring error in our CI environment Artifactory build plugin that pushed the artifacts to Bintray and Maven Central respectively. If there are problems, please let us know by re-opening this ticket. Thanks.
        Hide
        John Blum added a comment -

        Moved to the 1.3.4 Release.

        Show
        John Blum added a comment - Moved to the 1.3.4 Release.

          People

          • Assignee:
            John Blum
            Reporter:
            Frank Moley
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: