Best Of
Re: Configuring two Communal Storages in Vertica Eon Mode
we dont support multiple communal storage locations for single eon cluster.
Re: Any insights
create table should be completed quickly. if it is taking long time, please create a support ticket.
Re: Inconsistent behavior of inherited privileges when table moved to another schema
@SruthiA
Opened case 02819881
Thank you
Sergey
Re: Scheduling DROP_PARTITIONS on vertica
Hi prad33p2301,
You can put your logic into a stored procedure then schedule it in-database:
https://docs.vertica.com/24.1.x/en/extending/stored-procedures/executing-stored-procedures/triggers/scheduled-execution/
Re: Vertica driver for VSCode SQLTools does not provide audit information
Works!
Client type reported as Node.js Driver, and label by default set to VSCode SQLTools Vertica driver. It is as good as it can be.
Audit fields populated properly.
I can see client_os_hostname is populated without domain name. It is strange because everybody else populates with domain. It can be a client OS settings. Quite possible some method in Node.js return hostname without domain.
I think we should circle back to developer and ask to confirm that hostname is populated in full with domain.
Re: Assigning values within Stored Procedures
Behavior changed in 23.3.0 where stored procedures, including nested procedures, run in a single transaction, where previously each statement auto-committed. This means that "now()" will return the same timestamp unless there is an explicit PERFORM COMMIT in the stored procedure, and then it will still report the same timestamp each time it is called in the new transaction. Please see the release note at https://docs.vertica.com/23.3.x/en/new-features/23.3/stored-procedures/
To get elapsed time for the script, use "clock_timestamp()" instead of "now()" to get the system time rather than the transaction time.
Re: ranged projections aren't superprojections when adding columns?
Projections that include all columns and rows of the anchor table can be considered superprojections in Vertica.
Therefore, ranged projections, even if they include all columns, would not be counted as superprojections
as they do not cover all rows of the table.
Re: Node Dependencies, not including unsegmented projections
Thanks all. Old tables with ksafe different to standard. I've now fixed that and node dependancies look good.
Re: Node Dependencies, not including unsegmented projections
select VERIFIED_FAULT_TOLERANCE from projections should show any projections with higher ksafe. could you please share the output of below query
select sum(separated_bytes)/(sum(to_separate_bytes)+sum(separated_bytes)) * 100 as percentage_separated, sum(transferred_bytes)/(sum(to_transfer_bytes)+sum(transferred_bytes)) * 100 as percentage_transferred
from REBALANCE_TABLE_STATUS;
Re: Node Dependencies, not including unsegmented projections
select get_node_dependencies('1110') will show you the projections that are aligned in that way. There are 4 of them. Looks like you have some projections that were built as Ksafe=2. You can drop the "b2" projections for these, and that will fix it. It's not really a problem, but they are certainly unnecessary and just taking up extra disk space.