The Elasticube failed to complete query request (Connection lost)

Comments

6 comments

  • Avatar
    Nouman bhatti

    Is there any response to this error?

    0
    Comment actions Permalink
  • Avatar
    Michael Becker

    @Nouman - it was fixed in one of the latest releases. Which release you are on?

    0
    Comment actions Permalink
  • Avatar
    Nouman bhatti

    6.6.1

    0
    Comment actions Permalink
  • Avatar
    Michael Becker

    @Nouman - then check if memory is peaking up to your maximum memory, during the step where ElastiCube build fails. Anyway I think it would be worth rising a ticket with support, they will definitely help you establish root cause.

    Regards,

    Michał

    0
    Comment actions Permalink
  • Avatar
    Sam Ovenshine

    Michael is correct - the error can indicate an issue with performance, but it can also simply mean an issue with the query. First I would try to preview the table and make sure you are seeing results as expected. I would check for any dependencies on your custom field that are missing.

    I just tried to replicate the issue in 6.6.1 HF3 for two scenarios - 1. Creating a Custom SQL expression table with a duplicate field (for example, "SELECT Quantity, Quantity FROM ORDERS") and 2. Creating a Custom Field on a base table whose formula is a reference to an existing field in the base table (for example, a new field on ORDERS with a formula of [Quantity]). In the first case, Sisense automatically aliased the duplicate field and the build ran successfully. In the second case, Sisense would not accept a duplicate field name (I couldn't call the field Quantity but could call it Quantity1), and the build ran successfully as well.

    So this should work on the latest release. To Michael's point, I can't speak to the behavior on earlier versions. If you are still experiencing issues, please open a support ticket.

    1
    Comment actions Permalink
  • Avatar
    Rahul Ghadge

    I faced the similar issue. And one mistake that I did was - I only used to parse the expressions before starting the build. Whereas you should always check the preview and confirm that you are able to see the data. Because many times I have observed that the query/expression is correct syntaxwise but it may give some runtime error which would cause the build to fail with above error.And only way to avoid it is by checking the preview because you will get the error details in the preview and then you can correct the query/expression.

    0
    Comment actions Permalink

Please sign in to leave a comment.