searchable bi-server: table ts_bi_server - column sk_dummy #233
Replies: 13 comments 5 replies
-
Hello James, |
Beta Was this translation helpful? Give feedback.
-
Proprietary
Hi, There was no upgrade during 23-28 January.
From: Aadi1016 ***@***.***>
Sent: Friday, May 9, 2025 12:07 PM
To: thoughtspot/cs_tools ***@***.***>
Cc: Lenihan, James ***@***.***>; Mention ***@***.***>
Subject: Re: [thoughtspot/cs_tools] searchable bi-server: table ts_bi_server - column sk_dummy (Discussion #233)
EXTERNAL EMAIL– Use caution with any links or file attachments.
Thank you for the information James.
Was there an upgrade in cluster during this period?
—
Reply to this email directly, view it on GitHub<#233 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMS7PVAICWYHE6WUMRWFP6L25RV5BAVCNFSM6AAAAAB4YIEYGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBYGY2TCMY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
The incident_id represents the user action performed on the tool, while sk_dummy is a technical key created to ensure each row in the table is unique. In short, incident_id identifies the action, and sk_dummy guarantees uniqueness at the row level. |
Beta Was this translation helpful? Give feedback.
-
Public
Yes, I understand that – but I don’t understand why I have 2 of the same incident_ids, why did the 2nd incident_id get created?
From: Aadi1016 ***@***.***>
Sent: Friday, May 9, 2025 4:52 PM
To: thoughtspot/cs_tools ***@***.***>
Cc: Lenihan, James ***@***.***>; Mention ***@***.***>
Subject: Re: [thoughtspot/cs_tools] searchable bi-server: table ts_bi_server - column sk_dummy (Discussion #233)
EXTERNAL EMAIL– Use caution with any links or file attachments.
The incident_id represents the user action performed on the tool, while sk_dummy is a technical key created to ensure each row in the table is unique. In short, incident_id identifies the action, and sk_dummy guarantees uniqueness at the row level.
—
Reply to this email directly, view it on GitHub<#233 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMS7PVBKJCB3MYL4JLWHNIT25SXIHAVCNFSM6AAAAAB4YIEYGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBZGE2TEOI>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
Are those duplicate incident_id appearing for the same date or different dates? |
Beta Was this translation helpful? Give feedback.
-
Proprietary
The duplicates all have the exact same datetime.
That’s why I can’t figure out why there’s duplicates – as every column is identical in both rows except for sk-dummy.
From: Aadi1016 ***@***.***>
Sent: Friday, May 9, 2025 5:02 PM
To: thoughtspot/cs_tools ***@***.***>
Cc: Lenihan, James ***@***.***>; Mention ***@***.***>
Subject: Re: [thoughtspot/cs_tools] searchable bi-server: table ts_bi_server - column sk_dummy (Discussion #233)
EXTERNAL EMAIL– Use caution with any links or file attachments.
Are those duplicate incident_id appearing for the same date or different dates?
—
Reply to this email directly, view it on GitHub<#233 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMS7PVBKO5LDUZXKRGOIIQ325SYMDAVCNFSM6AAAAAB4YIEYGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBZGE4DMMA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
Can you tell what is the difference between their sk_dummy value? is it the sq number at the end? |
Beta Was this translation helpful? Give feedback.
-
Proprietary
Yes, the number at the end.
Thanks,
James
From: Aadi1016 ***@***.***>
Sent: Friday, May 9, 2025 5:38 PM
To: thoughtspot/cs_tools ***@***.***>
Cc: Lenihan, James ***@***.***>; Mention ***@***.***>
Subject: Re: [thoughtspot/cs_tools] searchable bi-server: table ts_bi_server - column sk_dummy (Discussion #233)
EXTERNAL EMAIL– Use caution with any links or file attachments.
Can you tell what is the difference between their sk_dummy value? is it the sq number at the end?
—
Reply to this email directly, view it on GitHub<#233 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMS7PVEYMXS5WQRQRQHGPVD25S4TBAVCNFSM6AAAAAB4YIEYGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBZGI2DQOA>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
Proprietary
Hey guys, on a more serious note our weekly CS_tools searchable-metadata failed last night. See the file attached?
Has something in the code changed over the last few days?
Unfortunately, I can't forward any logs of the error - the local logs haven't being created (for a number of months) since a process change in databricks. Nick actually raised an issue directly with databricks but I guess it hasn't been resolved.
Is there anything you can do to get the searchable-metadata back running successfully.
The 2 CS_tools liveboards are used quite extensively by our end customers.
Regards,
James
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
Proprietary
Sorry - here's the screenshot of the error that returned to screen.
Regards,
James
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
Hello James, |
Beta Was this translation helpful? Give feedback.
-
Proprietary
The process runs for about 10 seconds. Did something change last week?
From: TS-sumeet-jain ***@***.***>
Sent: Monday, May 12, 2025 3:35 PM
To: thoughtspot/cs_tools ***@***.***>
Cc: Lenihan, James ***@***.***>; Mention ***@***.***>
Subject: Re: [thoughtspot/cs_tools] searchable bi-server: table ts_bi_server - column sk_dummy (Discussion #233)
EXTERNAL EMAIL– Use caution with any links or file attachments.
Hi @333-Spur-Tmps<https://github.com/333-Spur-Tmps> ,
Can you please share how logs does the process runs for if its not possible to collect logs.
—
Reply to this email directly, view it on GitHub<#233 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMS7PVGTOW3M3KPEBGSIOZD26CIQRAVCNFSM6AAAAAB4YIEYGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRG43DONQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
-
Proprietary
Hi Guys,
Any update on the issue related to searchable/metadata command?
From: TS-sumeet-jain ***@***.***>
Sent: Monday, May 12, 2025 3:35 PM
To: thoughtspot/cs_tools ***@***.***>
Cc: Lenihan, James ***@***.***>; Mention ***@***.***>
Subject: Re: [thoughtspot/cs_tools] searchable bi-server: table ts_bi_server - column sk_dummy (Discussion #233)
EXTERNAL EMAIL– Use caution with any links or file attachments.
Hi @333-Spur-Tmps<https://github.com/333-Spur-Tmps> ,
Can you please share how logs does the process runs for if its not possible to collect logs.
—
Reply to this email directly, view it on GitHub<#233 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMS7PVGTOW3M3KPEBGSIOZD26CIQRAVCNFSM6AAAAAB4YIEYGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRG43DONQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (126 East Lincoln Ave., P.O. Box 2000, Rahway, NJ USA 07065) and/or its affiliates, that may be confidential, proprietary copyrighted and/or legally privileged. (Direct contact information for affiliates is available at - Contact us - MSD<https://www.msd.com/contact-us/>.) It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi admin,
I have a question around table ts_bi_server that is populated during the 'searchable bi-server' command. I expected incident_id to be the lowest grain in the table but I noticed a column sk_dummy (concatenation of cluster_guid & timestamp & seq_number) to be a lower grain and rarely but sometimes have one incident_id twice. These rows are identical except for sk_dummy,
What is the difference between columns incident_id and sk_dummy and what is the logic and reasoning behind sk_dummy?
Regards,
James
Beta Was this translation helpful? Give feedback.
All reactions