API create custom tables in Elasticube

Comments

5 comments

  • Avatar
    Moti Granovsky

    Hi Ricky,

    Modifying Elasticubes via REST API isn't supported in current versions of Sisense - there is a CLI that allows some modifications on legacy Elasticubes - those created in the Windows Desktop application as .ecube files - but not for new Elasticubes created via the Web UI.

    However, there will be brand new REST APIs for exactly this purpose. These APIs are currently being prepared for release, and should be out in the upcoming Linux release first, and in a Windows release slightly later.

    0
    Comment actions Permalink
  • Avatar
    Ricky Lui (Edited )

    Hi Moti,

    Thank you so much. This is really helpful. Being able to modify cube and custom tables is quite important to integrate and document the work into Git processes. Really appreciate the effort in building up the API.

    Just to clarify, following the documentation found in https://sisense.karhoo.com/app/dev/#, what happens if I send a POST request to /elasticubes/{address}/{cubeId}/custom_tables? Would it only create a custom table in the Elasticube if the cube was created by a Windows Application? Otherwise nothing happens?

    On another note, where could I look up the releasing plan for the new APIs?

    Thanks again.

     

    Ricky

     

    0
    Comment actions Permalink
  • Avatar
    Ken Slattery

    If I read this correctly all the V1.0 REST calls to do things like create datasets and dataset tables don't work. Is that correct?

    My use case is that I want to provide a UI (Excel at first) for an Admin to select which fields they want to add to the eCube. I would then add these programmatically. The reason for this is that we will have 100s of tables and I don't want users to have to create them separately.

    PSM does this but it seems very slow. I want to use the API because I also need to do some things with dashboards for mutliple customers and that requires the API AFAIK. Does that work?

     

    Ken

    0
    Comment actions Permalink
  • Avatar
    Moti Granovsky

    Ricky - yes I believe the way you described it is accurate. In essence, "legacy" Elasticubes created by the windows application (Elasticube Manager) were created in encoded XML format (.ecube) and stored on the hard drive as physical files, while the new web UI stores them in the application database as JSON objects.

    Neither PSM.exe nor those v1 REST APIs were built to manipulate said JSON format, and while some have been adapted to be compatible over time (and thus may work, for example on a running Elasticube) they aren't fully compatible, and I personally believe they aren't very friendly to use either.

    Due to these factors, we decided to design and develop a set of brand new APIs (as v2) from the ground up, sticking to a much stricter REST standard, defining each resource in depth, and supporting all the actions we could. As you can imagine that's no small undertaking and multiple teams have been collaborating for the past few months to make this happen.

    I'm very excited to see this new set of endpoints come out, partially because I designed them and partially because they have been requested by so many of our users!

    Ken - Yes, to an extent (as you can see in my explanation above) these REST endpoints won't work in some cases. Your use case, of automating Elasticube schema generation is the main use case we're aiming for with the new APIs. There are many existing implementations using PSM.exe and they work well, but everyone prefers REST! :)

    0
    Comment actions Permalink
  • Avatar
    Sisense Karhoo

    Hi Moti,

    Thank you for the detailed explanation and that has surely cleared things up. I am wondering whether you have a rough timeline for the v2 API release? It would be of great help as we would like to integrate with the new API asap.

    Ricky

    0
    Comment actions Permalink

Please sign in to leave a comment.