Member since 
    
	
		
		
		10-16-2013
	
	
	
	
	
	
	
	
	
	
	
	
	
	
			
      
                307
            
            
                Posts
            
        
                77
            
            
                Kudos Received
            
        
                59
            
            
                Solutions
            
        My Accepted Solutions
| Title | Views | Posted | 
|---|---|---|
| 12385 | 04-17-2018 04:59 PM | |
| 7626 | 04-11-2018 10:07 PM | |
| 4379 | 03-02-2018 09:13 AM | |
| 24556 | 03-01-2018 09:22 AM | |
| 3379 | 02-27-2018 08:06 AM | 
			
    
	
		
		
		12-04-2017
	
		
		09:03 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thanks for following up! Do you mind summarizing the changes you made to fix it so others can benefit from your solution? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		11-28-2017
	
		
		05:00 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 It's generally safe to use name-based resolution by default. Performance should be about the same. I agree name-based resolution may be a better choice because it's more intuitive.     Index vs. name based resolution have different tradeoffs in terms of what schema-evolution operations are allowed. For example with index-based resolution you can safely rename a column in your table schema. With name based resolution you can safely add/drop columns in the middle of your table schema, whereas with index-based resolution you can generally only add new columns at the end. So it's really all about tradeoffs. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-27-2017
	
		
		08:55 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Please also see my response on the JIRA. In addition:     The fact that the JIRA is old has no bearing on priority. We prioritize according to the needs of our users. We have limited resources and make difficult choices on what to work on. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		10-10-2017
	
		
		08:08 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Thanks for following up! Glad you got it working. 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-11-2017
	
		
		08:17 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 It has been a long time since this question was answered.  Has there been further recommendation by Cloudera on this ? Does cloudera support STRING data type to be used to store BINARY data ? or its something that works today and may stop working tomorrow ? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-07-2017
	
		
		09:22 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
	
		1 Kudo
		
	
				
		
	
		
					
							 Nad1998, that's a different error - it means your 'products' table does not exist or is not visible to Impala (try running 'invalidate metadata products', then retry query). 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		09-05-2017
	
		
		09:03 AM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 Is there any work around for this issue? 
						
					
					... View more
				
			
			
			
			
			
			
			
			
			
		
			
    
	
		
		
		08-24-2017
	
		
		04:01 PM
	
	
	
	
	
	
	
	
	
	
	
	
	
	
		
	
				
		
			
					
				
		
	
		
					
							 I'm afraid Impala is not yet able to recognize that only two partitions need to be scanned. We're aware of the gap and that specific optimization is tracked by:  https://issues.apache.org/jira/browse/IMPALA-2108     For now, you can manually rewrite your query as suggested in the JIRA as follows:  select id, yyyymmdd, group_id, test from dwh.table where  ((id='1a' and yyyymmdd=20170815 and group_id=1) OR (id='2b' and yyyymmdd=20170811 and group_id=2))  AND  ((yyyymmdd=20170811 and group_id=2) OR (yyyymmdd=20170815 and group_id=1))     or alternatively, use a union:     select id, yyyymmdd, group_id, test from dwh.table where  id='1a' and yyyymmdd=20170815 and group_id=1    union all  select id, yyyymmdd, group_id, test from dwh.table where  id='2b' and yyyymmdd=20170811 and group_id=2    
						
					
					... View more