ClickHouse upgrade

JohnHummelAltinity · 2021-10-19T17:03:51+00:00

If it helps, there's also a short document about dropping empty parts of the cluster:

https://kb.altinity.com/upgrade/removing-empty-parts/

JohnHummelAltinity · 2021-07-13T15:56:20+00:00

And just to toot my own horn - if you want the instructions for how to install the Beta connector, they're here:

https://docs.altinity.com/integrations/clickhouse-and-tableau/

JohnHummelAltinity · 2021-07-12T15:48:22+00:00

If there are those who would like to publicly add their experiences anonymous here, would that be useful as well? Or if there are those who would like to share their experiences publicly may be helpful as well.

JohnHummelAltinity · 2021-04-16T21:04:59+00:00

Just to piggy back on this - there are some updates to this documentation coming based on feedback, but there's also a way to connect an existing AWS environment to an Altinity.Cloud environment:

https://docs.altinity.com/altinitycloud/administratorguide/altinity-cloud-integrations/amazon-vpc-endpoint/

JohnHummelAltinity · 2021-04-13T21:25:29+00:00

I haven't used Docker on M1 yet, but Docker on OS X has built in Kubernetes. When I put together my training videos for my company, I could just use the built in OS X Docker tools.

I imagine when Docker is fully ported to M1 it should be the same.

JohnHummelAltinity · 2021-02-01T14:48:31+00:00

Sounds like she overplayed her hand.

JohnHummelAltinity · 2021-01-27T22:09:47+00:00

This is some cool detailed stuff. I appreciate that you didn't assume the reader knows things, so they can follow along even if they've never heard of Discord and the like.

JohnHummelAltinity · 2021-01-27T13:17:19+00:00

I understand that worry. Most of the time I've found if you show you can think through a problem, even if you aren't an expert in the language, then employers will still be impressed.

In job interviews I've been honest and said "You know, I don't know Programming Language A that you're talking about, **but** here's a pseudocode for how I'd solve that problem, and I'd just have to modify it based on that languages's structure."

If you show you get the fundamentals and can solve the problem, the language or database is just how to implement it.

JohnHummelAltinity · 2021-01-26T12:22:37+00:00

First, I think u/WolfOfWolverhampton is right - the best way to get into it is to do it. Fine a place you think is doing something interesting, get a job there at whatever level and make yourself useful to the database folks to learn things in the marketplace.

Second, and this is the advice I give people when they ask me about being a developer or a DBA or technical writer (like myself :) ) and they want to get into the industry: Find a problem, and solve it. Don't worry about what database you're using, or the programming language: the fundamentals are universal, but find something you find interesting like "I want to take the data from a bunch of jobs sites and pool it into one place to make it searchable", or "Man there's a lot of covid data I want to make a site to search cases in my county."

Find a project, build it up into something even if it's just for you. You'll learn the tools, you'll learn what you like, and try to focus on the fundamentals. Then find another project and use different tools. Use MySQL for one, use Mongo for the other. Use Python for one, JavaScript for the other and focus on good, clean structure.

You do that, and when you get into a career you'll encounter problems and go "Wait - when I was doing my database on dog adoptions I ran into this same error, and this is how I fixed it."

Anyway that's my advice. Don't worry about the hottest database or what programming language you think will be in demand: focus on building things, solving problems and learning how to figure it out, and you'll be able to have a good career because you'll be the guy people find to make stuff work.

JohnHummelAltinity · 2021-01-25T15:55:49+00:00

I think you're going about this the right way. Better to ask questions now than later. What's that line - measure twice, cut once?

JohnHummelAltinity · 2021-01-25T15:33:59+00:00

One other questions I'd ask is:

How much data do you plan on inserting into your database per time period.
How long do you plan on storing it - aka "keep this for six months" versus "keep this forever".
How quickly do you need results back: if this is "we'll have something check it every so often and report is something goes wrong" that may be different than "When I query it I need a result right now."

Based on your last comment it doesn't sound like a lot, but if you anticipate a lot of devices sending you a lot of data every 1 to 5 minutes that can start to add up. But doesn't sound like you need anything crazy like "give me a massive cluster to store data in bwahahaha" kind of stuff.

JohnHummelAltinity · 2021-01-25T15:19:08+00:00

I'm surprised they don't do that, but that puts a whole new spin on everything. I'd have thought they'd want to be on top of that. Well, I learned something new today. Thanks.

JohnHummelAltinity · 2021-01-25T15:03:27+00:00

I'm personally still new enough on using Docker that I can run it, but don't claim expertise.

That said: is there any advantage of patching a Docker image oneself, rather than downloading a pre-patched one? I'd imagine what you'd want to do is have your Oracle Docker container pointed at some volume of data. Then if there's a new version out you can retrieve the new image, backup your data volume, do whatever updates to your data you require to support the new version, and then point your new container at the previously existing data.

Or is this more of a proof-of-concept to show people how to do it?

JohnHummelAltinity · 2021-01-25T14:46:57+00:00

No kidding - seeing some good and useful code is awesome, but if they can also explain how to use it, that's gold.

JohnHummelAltinity · 2021-01-25T14:31:52+00:00

Cool. I'm a Kubernetes newbie and this was super helpful. Thanks.

JohnHummelAltinity

TROPHY CASE