-
Notifications
You must be signed in to change notification settings - Fork 13
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
Slave mode broken for WMTS layers with dimensions #300
Comments
Isn't related to #299? |
For me this:
or better:
and the dimension will be get in the |
No, it's not related to #299. All my layers have the same dimension. |
It's not that easy. In that context, |
Effectively, but I don't understand what's different with local one... |
In local mode, we generate for every combination: tilecloud-chain/tilecloud_chain/generate.py Lines 41 to 47 in c3b2a2b
By the way, I see that the master is doing that as well. But I guess the values oare not passed in SQS and the slave, with my PR, will do only the same set of values every times. |
And it's don on master, then we will have an SQS messages for each dimension, not? |
I've just tried to do it, but it's a huge change that involves changes in tilecloud as well: a lot of places take only the TileCoord as parameter and expect the dimensions as member of the class. We need all those places to take the Tile as parameter and remove the dimensions member. We don't have time for that. Can't we just take my hackish PR for the moment and leave this issue open to remember to do a proper fix? |
Fixed with #314 |
My layer is configured like that:
When starting the slave, it fails wih this stacktrace (I've included the 2 debug prints I've added to understand the problem:
I can trace back the empty dimensions parameter to this line:
tilecloud-chain/tilecloud_chain/generate.py
Line 49 in 29ca2f1
But I don't know what to do, here.
The text was updated successfully, but these errors were encountered: