Member since 
    
	
		
		
		07-17-2017
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                143
            
            
                Posts
            
        
                16
            
            
                Kudos Received
            
        
                17
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 1976 | 07-03-2019 02:49 AM | |
| 2186 | 04-22-2019 03:13 PM | |
| 1712 | 01-30-2019 10:21 AM | |
| 9466 | 07-25-2018 09:45 AM | |
| 8559 | 05-31-2018 10:21 AM | 
			
    
	
		
		
		10-31-2017
	
		
		03:22 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Remark: I observe in ClouderaODBCDriverforImpala_connection_0.log file, that the PrepareTResultForDataRetrieval in the 2 cases repeats ~150 times, even if the RowsFetchedPerBlock is 10000 (it look like it fixed on 1024) !!! 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-26-2017
	
		
		05:06 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @EricL    I already increase the RowsFetchedPerBlock and also TSaslTransportBufSize and no improvement :'(  In Additionally, the test of ODBC with postgresql driver is runed with the same value of this proprieties and give a good results (50 secs). 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-25-2017
	
		
		05:06 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thanks to your reply @EricL    I fetched same result of query on a file (about 500Mb), then I copied it with scp command to the first remote server, and it finished in ~40 seconds.    To elimine the probability that this issue is caused by a network speed, I have been copied the same results (9.2M) in a postgres table and test the fetchAll with postgres driver via unixODBC and it takes about 50 secs.   
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-21-2017
	
		
		10:27 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Hi,    In NameNode when I run the query via odbc script (php/perl or python), I can fetchAll results (9.2M) in a variable in about 30 seconds, but when I tried with the same script/query on another remote 2 servers, the execution time was in first server 28 min and in second 17 min.    To exclude the assuming that it's a network speed issue, I fetch the result on a file and then I copied it with scp command to the first remote server, and it finished in ~40 seconds.    What I observe in Query info in CM that there is a big different between the *Threads: Network Send Wait Time* values in the 3 queries :    in NN query: 9.40s  in 1st remote server: 16.7m  in 2nd remote server: 26.8m    And also I try an java script with Impala JDBC, but the results in NN are already not stimulate to continue.    But so far I cann't find where is the problem and how can I resolve it.    NB: I'm working on CDH 5.12.0/Impala 2.9.0, I installed Impala ODBC 2.5.37.1014.       Hope you can respode to me ASAP, because this issue is a realy an obstacle of using a cluster that we made a several months to make it.  Thanks in advance. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
 - 
						
							
		
			Apache Impala
 - 
						
							
		
			Cloudera Manager
 
			
    
	
		
		
		10-06-2017
	
		
		10:13 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Yes man, that what I do now in *drop* statement, but so far no easy solution for *alter*.  Thanks again @EricL 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-03-2017
	
		
		03:58 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi @EricL,  Thanks for the replay,    Can you give me the JIRA track link of this issue please ?  And about 'hive.metastore.client.socket.timeout' I find 3 config variables with the same name:    1- Hive: Hive Metastore Connection Timeout (5m).  2- Hive: in : Service Monitor Client Config Overrides (value: 60).  3- Impala: Catalog Server Hive Metastore Connection Timeout and Impala Daemon Hive Metastore Connection Timeout (value: 1h).    Can you help me to know which one is the concerned ?    Hope this issue iresolved ASAP.  Thanks again. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-02-2017
	
		
		09:26 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thank you very muth for the answer man    I tried to drop it with the hive, but it give this error message:      hive> drop table cars;
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:hive.metastore.sasl.enabled can't be false in non-testing mode)  I think it's another problem that we have to fix, did you have any idea ?  NB: I use Sentry with hive. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-02-2017
	
		
		04:01 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							Note: I use Impala Shell v2.9.0-cdh5.12.0 (03c6ddb) built on Thu Jun 29 04:17:31 PDT 2017  Thanks in advance.
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-26-2017
	
		
		04:22 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi,    I have a partitionned tables that have more than 50k partitions, it work a good except the Hive Metastore operations, like DROP and ALTER ... RENAME, I face this error message:      Query: drop table cars
ERROR: ImpalaRuntimeException: Error making 'dropTable' RPC to Hive Metastore: 
CAUSED BY: MetaException: Timeout when executing method: drop_table_with_environment_context; 600003ms exceeds 600000ms  I don't now if it's, a memory problem, or it's normal and I should adjust the timeout value.. ? if yes, which one ?    Thanks to help me ASAP. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
		
			
				
						
							Labels:
						
						
		
			
	
					
			
		
	
	
	
	
				
		
	
	
- Labels:
 - 
						
							
		
			Apache Hive
 - 
						
							
		
			Apache Impala
 
			
    
	
		
		
		08-28-2017
	
		
		03:23 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Hi    I found the solution by adding two antislashs before the old two.      --null-string '\\\\N'
--null-non-string '\\\\N'    Thanks @wsch for your replay. 
						
					
					... View more