Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesThe designing interface is very slow when we design an in-db workflow.
The reason of that is that Alteryx connects everytime he needs to refresh the data. Example on Hive :
Mar 20 15:28:49.453 DEBUG 6048 HardyConnection::Connect: Default branding specific auth mech: 2 Mar 20 15:28:49.453 DEBUG 6048 HardyHiveClientFactory::CreateClient: Create HS2 client. Mar 20 15:28:49.453 DEBUG 6048 HardyHiveClientFactory::GetBackendCxnPool: Create session manager. Mar 20 15:28:49.453 DEBUG 6048 HardyHiveClientFactory::GetBackendCxnPool: Create backend connection pool. Mar 20 15:28:49.453 DEBUG 6048 HardyHiveCxnPool::GetHS2Cxn: Create HS2 connection. Mar 20 15:28:49.453 DEBUG 6048 HardyHiveCxnPool::GetCxnFactory: Create backend connection factory. Mar 20 15:28:49.453 DEBUG 6048 HardyHiveCxnFactory::CreateHS2Cxn: Create HS2 HTTP transport. Mar 20 15:28:49.453 DEBUG 6048 HardySessionManager::GetSession: Getting new session handle. Mar 20 15:28:50.399 DEBUG 6048 HardyTCLIServiceThreadSafeClient::OpenSession: TOpenSessionReq client_protocol = HIVE_CLI_SERVICE_PROTOCOL_V1
Maybe we could have an option on the IN DB Connection configuration to stay connected while designing (maybe with a limit time).
(PS : we also tried the option to Disable Auto Configure, it's clearly not he solution)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.