OK mate thx for the prompt response and hope all is well with you! :)

Leigh
https://tilleytech.com/

Hey Leigh,

Happy to hear from you and Happy New Years as well! In regards to your question, we recently moved from poetry to uv and so the installation instructions should now be as follows (when at the root of the repo directory):

pip install uv
uv sync --python 3.10.11
uv run jupyter-lab

Let me know if this works for you!

Hmmmm.... It should just work. Can you make sure that you pull the latest from our GitHub repository?

In other words:

git checkout main
git pull

Then do:

pip install uv
uv sync --python 3.10.11
uv run jupyter-lab

Let me know if that works for you!

I think you may have to do the following:

git checkout main
git pull
git reset --hard origin/main

to get to the latest commit of the main branch. Note that doing this will overwrite your local changes with the latest files from main, but I think this is exactly what you need to fix your problem.

This is because I see you're getting the error about your local changes possibly getting overwritten by merge when doing a git pull, which is preventing you from pulling the latest files. Hence, why uv is complaining about not having a proper pyproject.toml, since you don't have the latest pyproject.toml.

Try the above and then do:

pip install uv
uv sync --python 3.10.11
uv run jupyter-lab

I think this should unblock you, but let me know!

Perfect, I think what I'm seeing from your screenshot are some errors from the syntax shift from 0.8.X to 0.9.X but that could also be because your tutorial.ipynb file is from 5 months ago haha. If you have any further issues, don't hesitate to let me know — I'll be here!

Cheers 🍻
Andrew

and it copies down a file that has a date of 12 Aug 2024. So is this the old one then? As this command is still up on the Atoti installation page.

Hmm let me look into this. If this is copying the old tutorial then that's something to bubble up to the R&D folks. Thanks for letting me know!

Checking back in, the resulting notebook for python -m atoti.copy_tutorial tutorial works for me for the latest version 0.9.3. My suspicion is that you may have previously used the base python on your local machine when executing python -m atoti.copy_tutorial tutorial, which stayed the same version as last time (probably 0.8.X).

Instead, since we're using uv, you'll have to run that command from within the virtual environment created by uv by doing uv run python -m atoti.copy_tutorial tutorial and then doing a uv run jupyter-lab. I think this should work for you moving forward but let me know otherwise!

As a comparison, you can probably see a difference when you do:

pip list | grep atoti

vs.

uv pip list | grep atoti

Note: If you're using Windows, you may have to do findstr atoti instead.

FYI, to fix this deprecation warning, you might want to try something like this:

import atoti as tt
from urllib.parse import urlparse

session = tt.Session.start(
    tt.SessionConfig(
        user_content_storage="./content",
        port=9092
    )
)

url = session.url
port = urlparse(url).port

This was a change going from Atoti Python API 0.8 to 0.9, you can find more of these types of changes outlined in https://www.atoti.io/articles/upgrading-to-atoti-python-api-0-9-0/!

Hey

Thanks and no worries. I wasn't displaying it as a complaint or moan, it was to highlight that it was a newer version thus some old calls are deprecated. :)

And then also a screenshot using my own custom C# DLL which speaks to remote cubes which I made to use with a project I'm slowly working on.

Haha sounds good, well if you have any other questions/concerns/comments, you know where to find me :) — good luck!

Hey Leigh,

Can you provide some more context on what you're trying to achieve here? Based on what I see, it looks like you're trying to connect to the Atoti database and pull some data, right? If so, I think what you may be looking for is making a request to our REST API that should return/respond with the data that you want. You can check out the following documentation for this: https://docs.activeviam.com/products/atoti/server/latest/docs/rest-api/database_rest_api/.

Note: The Atoti Server is bundled with Atoti Python API, so even though the docs say Atoti Server, the information therein should still be applicable even if you're using Atoti Python API to spin up your Atoti application.

Or since you're saying you're porting custom code to Java, it may be helpful for you to try out our Atoti Java API as well: https://github.com/activeviam/atoti-spring-boot-template

Of course, if I'm misunderstanding your use case here, let me know and I can try to re-asses my answer or loop someone else in who may have more information for you. Let me know!

Thanks,
Andrew

Hey Leigh,

Can you re-state your question one more time? I conferred with my colleagues but I think we may need a clarification on the exact question that you're looking for.

My understanding is that you're trying to perform a custom implementation and use https://github.com/olap4j/olap4j, but this doesn't seem to be working for you with Atoti. Though the reason you're using https://github.com/olap4j/olap4j is because you want to not only connect to Atoti via your custom application but also other OLAP vendors/applications as well, correct? And that the final follow-up question is if we have any recommendations or toolkits to help solve your issue/unblock you?

Hmmm... Yeah unfortunately I don't think we can really provide support here in terms of your custom implementation. As you had mentioned, https://github.com/olap4j/olap4j's last commit was 9 years ago, and when I inspect a bit further here it looks like the devs had wanted to enhance compatibility but never got around to it. I suspect that's what you're seeing in your code, where the compatibility of the olap4j library itself is just too outdated and hence why using it to connect to the Atoti cube is giving you hiccups.

Though have you tried the example illustrated on their GitHub README? https://github.com/olap4j/olap4j?tab=readme-ov-file#writing-a-simple-program. I know you're trying to use the XMLA driver but I see you're implementing it differently than what they show in their example. Could be worth a shot, but if it doesn't work with our XMLA endpoint (e.g. localhost:9090/xmla) I would chalk it up to compatibility issues of an outdated library.

Regarding any advice on how to unblock you? Unfortunately, I think that's outside of the scope we can provide support for. We can help support you on how to use Atoti and any issues that arise directly from within the Atoti ecosystem, but we may not be the best resource for triaging other third-party libraries' compatibility with Atoti. Sorry, we hope you can understand and apologies we can't be of more help 🙏