[yugabyted] Is the OSS version (Installed with helm chart) compatible with Hasura

[ammirator-administrator]

Jira Link: DB-11182

Description

Is Hasura compatible with Yugabyte?
I have a yugabyte db started using the official Helm chart
And hasura successfully connects to it, but when running the migrations for some reason hasura tries twice to run these and then fails because tables already exists
There is no useful logs at all in tserver or master everything seems to run ok
But hasura when running the migrations says that table already exists, I assume it may fail to read the schema and that's why it tries to run twice or it cant write to hdb_catalog schema which is the schema that hasura uses
I already did read the docs, in all docs it is said about hasura cloud or yugabyte cloud
But there is no example of self hosted hasura + yugabyte self hosted

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.

[ammirator-administrator]

Details:
I found that migrations after these are run are not marked as true

{
  "settings": {
    "migration_mode": "true"
  },
  "migrations": {
    "default": {
      "1661116054381": false,
      "1661184404940": false,
      "1661184404942": false,
    }
  },
  "isStateCopyCompleted": true
}
``

Can that be that Yugabyte doesnt support some JSON method which tries to write to DB and cant??

[ddorian]

Is the OSS version

The OSS version is the same as enterprise, same codebase.

(Installed with helm chart)

You have to specify what version you installed.

And what version of Hasura.

And hasura successfully connects to it, but when running the migrations for some reason hasura tries twice to run these and then fails because tables already exists

Maybe Hasura expects to have transactional DDL (which we don't support) and tries to run them concurrently expecting the db-side to handle it.

Can that be that Yugabyte doesnt support some JSON method which tries to write to DB and cant??

I don't know? We have to see some type of error? At least an error message from hasura where it says the json function didn't exist.

[ammirator-administrator]

That's the problem there is no error at all)
Latest version of yugabyte helm chart
And latest version of hasura

But that doesn't matter much since I tried with different versions fro last releases

What I noticed in the yugabyte UI is that some initial queries also takes forever to run and hasura is not happy with that, I believe these tools are just not compatible, the queries to parse the schema in the db runs to slow
I just guess I'll have to use another solution
I also tried the cloud version and the schema parsing just takes a lot and hasura fails due to timeouts
Even to some data from some tables it can load which is strange
I would love to see a working tutorial on how to setup these two together to work, but so far all tutorials uses cloud versions even tho I also tried with cloud, so or I get to many connections errors (Which is not begginer friendly cause you have to use another plan even for testing and pay money, or queries are to slow, so picking yugabyte is hard cause you cant even test it before making a real decision)

[ddorian]

Latest version of yugabyte helm chart

And latest version of hasura

Please describe the exact versions.

What I noticed in the yugabyte UI is that some initial queries also takes forever to run and hasura is not happy with that

It's probably the queries for system views.

I also tried the cloud version and the schema parsing just takes a lot and hasura fails due to timeouts

The free cloud version is very underpowered.

But that doesn't matter much since I tried with different versions fro last releases

What's the cluster hardware of yb-tserver & yb-master?