You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One possible reason is that Sedona 1.6.0 added telemetry collection to SedonaContext initialization, it may take quite a long time if the driver node silently drops traffic to the internet. If you are running Sedona in a cluster without internet access, you can try setting driver's environment variable SCARF_NO_ANALYTICS to true to opt out telemetry collection and see if initialization is still slow.
One possible reason is that Sedona 1.6.0 added telemetry collection to SedonaContext initialization, it may take quite a long time if the driver node silently drops traffic to the internet. If you are running Sedona in a cluster without internet access, you can try setting driver's environment variable SCARF_NO_ANALYTICS to true to opt out telemetry collection and see if initialization is still slow.
the lazy initialization of sedona 1.6.0 is quite slower than sedona 1.5.1 , obviously
The text was updated successfully, but these errors were encountered: