Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cartodbfytable fails because of quota #1150

Closed
javisantana opened this issue Nov 14, 2014 · 3 comments
Closed

cartodbfytable fails because of quota #1150

javisantana opened this issue Nov 14, 2014 · 3 comments
Assignees

Comments

@javisantana
Copy link
Contributor

sometimes when you try to cartodbfy a table you get an error:

"please set user quota before cartodbfying tables"

I guess it's ont multiseat accounts, please @andrewxhill provide more information

see #874 (comment)

@Kartones
Copy link
Contributor

I'm getting something similar upon implementing a small change on the cartodb-postgresql extension, just running the tests:

*** /home/kartones/src/cartodb/lib/sql/expected/test/CDB_CartodbfyTableTest.out 2014-11-14 11:33:56.001112060 +0100
--- /home/kartones/src/cartodb/lib/sql/results/test/CDB_CartodbfyTableTest.out  2014-11-14 11:34:53.969111560 +0100
***************
*** 4,10 ****
  SELECT 1
  ERROR:  Please set user quota before cartodbfying tables.
  CONTEXT:  SQL statement "SELECT cartodb._CDB_check_prerequisites(schema_name, reloid)"
! PL/pgSQL function cdb_cartodbfytable(text,regclass) line 6 at PERFORM
  0
  single non-geometrical column cartodbfied fine
  DROP TABLE
--- 4,10 ----
  SELECT 1
  ERROR:  Please set user quota before cartodbfying tables.
  CONTEXT:  SQL statement "SELECT cartodb._CDB_check_prerequisites(schema_name, reloid)"
! PL/pgSQL function cdb_cartodbfytable(text,regclass) line 7 at PERFORM
  0
  single non-geometrical column cartodbfied fine
  DROP TABLE

So I'll investigate it

@Kartones
Copy link
Contributor

Wrong "alert", this was failing due to the way we do tests of the extension. In any case I'm going to make the extension update recreate the quota as we will introduce changes on counting it.

@Kartones
Copy link
Contributor

This issue will be fixed after #1138 because we now run a rebuild_quota_triggers upon each extension update (due to started changing quota calculation logic and probably changing again in the future)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants