Announcement

Collapse
No announcement yet.

Changes since 1.0

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Changes since 1.0

    Hi,

    is there a way to understand the changes since wire protocol doc version 1.0?

    I am seeing "Error sending procedure Insert to the correct partition. Make sure parameter values are correct." in response to a wire call that used to work with Volt beta.

    I am a bit at a loss how to find out what may have changed.

    Thanks a lot,

    Henning

  • #2
    Hi Henning, Thoughtfully, the

    Hi Henning,

    Thoughtfully, the actual exception is being swallowed. If you add an e.printStackTrace() to line 1322 of ClientInterface we can find the actual error.

    What is the signature of the procedure and the parameters you are sending?

    -Ariel

    Comment


    • #3
      Erlang client

      I guess I wasn't clear that I was talking about the Erlang client.

      I found around a dozen changes in the protocol meanwhile, so the message I cited above may be completely meaningless.

      Do you by chance have a list of changes to the wire protocol?

      Thanks,

      Henning

      Comment


      • #4
        Hi Henning, Can you be more

        Originally posted by henning View Post
        I guess I wasn't clear that I was talking about the Erlang client.

        I found around a dozen changes in the protocol meanwhile, so the message I cited above may be completely meaningless.

        Do you by chance have a list of changes to the wire protocol?

        Thanks,

        Henning
        Hi Henning,

        Can you be more specific about those changes?

        The wire protocol is still supposed to be accurate and we need to fix it if there is something incompatible.

        It is missing VARBINARY, but that doesn't break compatibility.

        Ariel

        Comment


        • #5
          errors in wire protocol spec

          Originally posted by aweisberg View Post
          Hi Henning,

          Can you be more specific about those changes?

          The wire protocol is still supposed to be accurate and we need to fix it if there is something incompatible.

          It is missing VARBINARY, but that doesn't break compatibility.

          Ariel
          I'm aware of at least this issue from scratching at a go client: https://issues.voltdb.com/browse/ENG-2770

          I also see in Jira:

          https://issues.voltdb.com/browse/ENG-2400
          https://issues.voltdb.com/browse/ENG-2305

          Comment

          Working...
          X