ANALYZE TABLE COMPUTE STATISTICS => change stats for the table
and should should it
ANALYZE TABLE COMPUTE STATISTICS for COLUMNS => change stats
for columns and should change it for columns but NOT for the table
That's it.
2016-06-16 21:10 GMT+02:00 Ashok Kumar :
> Greeting gurus,
>
> When I u
Ok use explain extended your sql query to see if the optimizer makes a good
decision.
Help the optimizer by doing stats update at column level
ANALYZE TABLE COMPUTE STATISTICS FOR COLUMNS
use desc formatted to see the stats#
HTH
Dr Mich Talebzadeh
LinkedIn *
https://www.linkedin.com/prof
*without any improvement of performance
17 июня 2016 г. 1:00 пользователь "Vadim Dedkov"
написал:
> Ok, thank you. I tried Hive with Tez for my index-problem without any
> performance
> 17 июня 2016 г. 0:22 пользователь "Mich Talebzadeh" <
> mich.talebza...@gmail.com> написал:
>
>>
>> Well I gues
Ok, thank you. I tried Hive with Tez for my index-problem without any
performance
17 июня 2016 г. 0:22 пользователь "Mich Talebzadeh" <
mich.talebza...@gmail.com> написал:
>
> Well I guess I have to agree to differ on this with Jorn as before.
>
> Vadim,
>
> Please go ahead and try what Jorn sugge
I explain. I can get result for count(*) with index table help, but I can't
realise how I can get result for *-select with index table help
17 июня 2016 г. 0:50 пользователь "Vadim Dedkov"
написал:
> >>If the optimizer does not pick up the index then you can query the index
> directly
> Could you
>>If the optimizer does not pick up the index then you can query the index
directly
Could you explain me, how I can do this for query like
*select * from my_schema_name.doc_t WHERE id = '3723445235879';*
?
Thank you
17 июня 2016 г. 0:03 пользователь "Jörn Franke"
написал:
> The indexes are base
Well I guess I have to agree to differ on this with Jorn as before.
Vadim,
Please go ahead and try what Jorn suggests. Report back if you see any
improvement.
Couple of points if I may:
Using Hive on Tez is not going to improve Optimiser's performance. That is
just the execution engine and BTW
The indexes are based on HDFS blocksize, which is usually around 128 mb. This
means for hitting a single row you must always load the full block. In
traditional databases this blocksize it is much faster. If the optimizer does
not pick up the index then you can query the index directly (it is ju
Nothing.
Hive does not support external indexes even in version 2.
In other words, although you create indexes, they are not visible to Hive
optimizer as you have found out.
I wrote an article on this hoping that we should have external indexes
being used .
HTH
Dr Mich Talebzadeh
LinkedIn *
Hello!
I use Hive 1.1.0-cdh5.5.0 and try to use indexes support.
My index creation:
*CREATE INDEX doc_id_idx on TABLE my_schema_name.doc_t (id) AS 'COMPACT'
WITH DEFERRED REBUILD;*
*ALTER INDEX doc_id_idx ON my_schema_name.doc_t REBUILD;*
Then I set configs:
*set hive.optimize.autoindex=true;*
*
Greeting gurus,
When I use
ANALYZE TABLE COMPUTE STATISTICS for COLUMNS,
Where can I get the last stats time.
DESC FORMATTED does not show it
thanking you
Hi,
Yes, that is correct. We have LDAPS configured on 636, and certificate
available only at that port. 443 is not enabled in our case, and should not
bother, since communication is performed just on 636.
2016-06-15 23:20 GMT-03:00 Anurag Tangri :
>
> Hey Joze,
> Ldaps is a different port like
12 matches
Mail list logo
