Even though the email claims otherwise, the refund was issued to my NRO account after some to and fro. I would have preferred if it was back to the foreign CC. You get less back due to their exchange rate calculation.
#airindia refund process is a borderline scam. Flight cancelled, they don't refund the charge back to your foreign CC only to a domestic savings account. As an NRI it's illegal to have a domestic savings account, their answer:
Most of the InnoDB row copy is not due to InnoDB design per se but the mysql storage engine API. Many simple row predicates should be able to select based on the key alone without materializing the rows at all. In the same mtr. You can generalize the interface to a sink which is specialized for different operations.
Iβve tried this in my experiments and you can go a long way with this design. These experiments are not on InnoDB code but the overall architecture is quite similar.
Not all the attendees at AWS Mumbai were from the industry. My message to the students and those starting out, who were interested in distributed systems and databases was - download the TiDB code, learn from a state of the art implementation and best of all contribute.
Latency is fairly easy to manage with a distributed cache in front of object storage. This distributed cache is a lot easier to get right because the SSTs are read only.
TiDB X architecture supports this. The Raft log is the source of truth and you can batch writes too because like a traditional storage engine you only need to ensure the writes are persistent when you move the raft log low water mark forward. An immediate write is not technically required when you persist the memtable. Itβs just simpler that way.
Iβve never used setjmp/longjmp in my programming career in production code. Played around with it to write crude coroutine libraries.
In C++ I think they lead to undefined behavior too. Never bothered with them after switching to C++.
Curious to know how people used them in production code.
I understand his broader argument, he is criticizing async/await and has a go at how different languages have tried and havenβt done a very good job with the exception of the implicit concurrency model used by languages like Go, Erlang, and Lua (via coroutines).
My point is that if all you have in your toolbox is color matching then good luck.
Nystrom's essay is great for explaining to a web developer why they can't magically use a blocking library inside a Node.js event loop without blocking the world. But if you're trying to orchestrate highly deterministic, parallel execution pipelines, treating concurrency like a simple "color matching" game is a fast track to unpredictable latencies.
I guess it's that time of the year again. "What color is your function?" is trending again. It has been 10 years, maybe it isn't "solved" because the entire premise is faulty. Nobody asks "what color is your data structure?" Everything in a codebase is "colored".
#airindia refund process is a borderline scam. Flight cancelled, they don't refund the charge back to your foreign CC only to a domestic savings account. As an NRI it's illegal to have a domestic savings account, their answer:
@airindia Dear #airindia , I have and I keep getting the same stock answer that I have posted above. I posted to X express my frustration with your process. Repeating the same line is not helping.