@xeraa@mastodon.social
@xeraa@mastodon.social avatar

xeraa

@xeraa@mastodon.social

🎩 of DevRel & Developer 🥑 at Elastic — toots about Elasticsearch, Kibana, search, observability, ops, security | he/him

This profile is from a federated server and may be incomplete. Browse more on the original instance.

xeraa, to random
@xeraa@mastodon.social avatar

turns out, you pay for every S3 request — even if it's returning an AccessDenied. just by knowing a bucket name (or picking one that's configured elsewhere) you can incur significant cost. "fun" story: https://medium.com/@maciej.pocwierz/how-an-empty-s3-bucket-can-make-your-aws-bill-explode-934a383cb8b1
guess security through obscurity still has value ;)

xeraa, to random
@xeraa@mastodon.social avatar

today marks my 8️⃣ year anniversary at . and it’s also a new start, since it’s my first day in SF to put us better on the map here — view from the office
PS: not an april fool‘s post 😅

andyide, to random
@andyide@fosstodon.org avatar

Any experts kicking around?

Postgres has a bunch of fuzzy string matching tools such as trigrams and phonetic algorithms but I couldn't find anywhere in Wagtail these are taken advantage of.

Docs keep saying if you want fuzzy match you need to use Elastisearch.

Ideally I'd like search to handle common misspellings - eg writing "vat" should get you "vets" in your search result. Or "hirse" should give you results for "horse".

Is there a plugin that does this anywhere?

xeraa,
@xeraa@mastodon.social avatar

@jochen @andyide there are now more specialized data structures that might help you? thinking about match_only_text as a first step: https://www.elastic.co/guide/en/elasticsearch/reference/current/text.html#match-only-text-field-type

xeraa, to Redis
@xeraa@mastodon.social avatar

unpopular opinion: with the relicense of , nothing changes for the vast amount of users
even if everyone loves drama and "parties with special interests" love to spread FUD. as a reminder, mongodb changed license in 2018 (https://www.mongodb.com/company/newsroom/press-releases/mongodb-issues-new-server-side-public-license-for-mongodb-community-server) — their users are fine

xeraa,
@xeraa@mastodon.social avatar

@xahteiwi I'm not part of redis but I'd assume they have mapped this out with lawyers pretty well (including the creation of their own license)
and IANAL and don't know their plans, but I'd assume they will keep the necessary copyright notices and the license file and then just move from there, since BSD is pretty commercial-friendly (see https://en.wikipedia.org/wiki/BSD_licenses#Commercial_license_compatibility)

xeraa,
@xeraa@mastodon.social avatar

@xahteiwi yes, but I'm not sure where "you must remove my contributions" would be covered in the BSD license. they'll keep the necessary notices (which is pretty much the only requirement in that license) and keep using it any way they see fit from there

xeraa,
@xeraa@mastodon.social avatar

@xahteiwi unlike the GPL, which differentiates between preamble and license, BSD doesn't specific the form very explicitly. not a lawyer but I'm not sure this is that big of a deal. also not sure if it's smart to do it like that though

xeraa, to random
@xeraa@mastodon.social avatar

"Redis Adopts Dual Source-Available Licensing": https://redis.com/blog/redis-adopts-dual-source-available-licensing/
Redis Source Available License (RSAL) or SSPL. they'll bundle the extra features (JSON, search,... which were under a free but non-OSI license already), called "Redis Stack" — I see where they are coming from

next up: a fork called freedis? 😅

xeraa,
@xeraa@mastodon.social avatar

@shochdoerfer didn't pay enough attention to who was pissing in their pool but possible
PS: it's fascinating how different the background for each of the relicenses is. for redis AWS was actually contributing a fair bit. with hashicorp they were partners. so every story there has its unique twist 😅

xeraa,
@xeraa@mastodon.social avatar

@shochdoerfer but does it matter? do they provide redis as a service to customers? or is this out of principle?

xeraa, to random
@xeraa@mastodon.social avatar

only took me 8 years at to do a joint talk with shay. while everyone in the background was shouting "developers" 😅

xeraa, to random
@xeraa@mastodon.social avatar

looking at cover letters in the age of LLMs is somewhere between painful and hilarious — though definitely wasting my time:
my proficiency in languages like [Additional Languages] and experience with [Technologies] complement my ability to contribute meaningfully

xeraa,
@xeraa@mastodon.social avatar

@shochdoerfer yeah. and the cover letter is optional. so why?!

fell, to random
@fell@ma.fellr.net avatar

I need to about stuff: Ever since the v4.2.5 update my is broken. It just says:

status: 503 org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized]

I already deleted the data directory, but when I tried to redeploy search according to the documentation, it gave me the same error message.

Any ideas what could've gone wrong?

xeraa,
@xeraa@mastodon.social avatar

@moira @fell this and a look what's in the log file — that should give some more pointers

xeraa,
@xeraa@mastodon.social avatar

@fell @moira ugh. it looks like this was either part of a cluster or got very confused with the upgrades?
in any case, if you don't have any relevant data in there, I'd delete it and start over — that should be the simplest approach. the one place that is important to delete is the data directory; maybe /var/lib/elasticsearch depending on your installation method or configuration (path.data is the setting). stop the node, keep the rest but delete that directory before starting again

xeraa,
@xeraa@mastodon.social avatar

@fell @moira you can build it yourself. I doubt that will solve your issue though
how do you install it (what's the binary) and the directory layout there? if you keep having leftovers from previous installations, we need to remove them (explicitly the data directory) to start a fresh bootstrapping

xeraa, to random
@xeraa@mastodon.social avatar

"Open Source Doesn't Require Providing Builds": https://codeengineered.com/blog/2024/open-source-not-builds/
yes, the expected norms are very far from the narrow coverage of what open source covers in the strict sense: no contributions, builds, tests (the anti-fork solution), community,… are all possible

box464, (edited ) to random
@box464@mastodon.social avatar

I'm playing around with mastodon 4.2 advanced search, digging into the code a bit. Really trying to do some trickery here but the devs have it pretty well locked down to exactly what is documented. I thought I could inject some elasticsearch precedence or other patterns but those are purely ignored (or cause issues with the search)

Honestly not sure if I'm even using the right syntax but looks close.

https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-simple-query-string-query.html

xeraa,
@xeraa@mastodon.social avatar

@cheeaun @box464 I guess the feature is just one PR away 😬
and while it makes sense to keep queries very cheap and not overload elasticsearch with anything funky, I also wanted that feature last week...

xeraa, to random
@xeraa@mastodon.social avatar

"10 reasons to upgrade to -py 8.x" — features, security, DSL, etc: https://discuss.elastic.co/t/dec-13th-2023-en-10-reasons-to-upgrade-to-elasticsearch-py-8-x/347292
PS: special thanks to @honzakral for keeping up the complaints until we got this sorted out 😬

xeraa, to random
@xeraa@mastodon.social avatar

what an achievement 🤮
not linking to the original source since this kind of stuff shouldn‘t get you any extra exposure (from twitter of course)

xeraa, to random
@xeraa@mastodon.social avatar

slides, so we don't have to be stuck on "this is fine": https://xeraa.net/talks/open-policy-agent-opa/
and thanks for having me (again) at devops.barcelona 😅

image/jpeg

xeraa,
@xeraa@mastodon.social avatar

@anderseknert I think it's a good sanity check for all the things rego can do but that it could also be more complex than what you were expecting at first 😅

xeraa, to random
@xeraa@mastodon.social avatar

some exciting ML stuff in the works: https://scrollprize.org/firstletters

xeraa, to hiring
@xeraa@mastodon.social avatar

we're a developer advocate in EMEA at . since the job title has taken on a very broad spectrum: on the technical side — "developer" is the first word for a reason. happy to answer any questions and you can find the details in https://jobs.elastic.co/jobs/eng/distributed-emea/senior-developer-advocate/5346896

PS: we'll have an opening for north america very shortly as well

xeraa, to random
@xeraa@mastodon.social avatar

and the full stack 8.10.1 is out. was leaking sensitive information in its logs (see https://discuss.elastic.co/t/kibana-8-10-1-security-update/343287), so upgrade away
elastic cloud should be patched up by us and it was the first time that we had to pull a release — fun weekend operation 🙈

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • provamag3
  • kavyap
  • DreamBathrooms
  • osvaldo12
  • magazineikmin
  • InstantRegret
  • everett
  • Youngstown
  • ngwrru68w68
  • slotface
  • rosin
  • GTA5RPClips
  • tester
  • PowerRangers
  • anitta
  • thenastyranch
  • mdbf
  • ethstaker
  • cisconetworking
  • Durango
  • vwfavf
  • normalnudes
  • tacticalgear
  • khanakhh
  • modclub
  • cubers
  • Leos
  • megavids
  • All magazines
    •