# 2026.2 ScyllaDB 2026.2 is a ScyllaDB release adding DynamoDB Streams compatibility, Vector Search, Trie indexes, and experimental strongly consistent tables. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Logpoints Walkthrough DevFeed: [Logpoints Walkthrough]() Original publisher: [Read original article]() Author: Igor Kulakov Published: 2026-09-16T14:14:04Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [debug](), [debugging](), [gRPC](), [Java](), [2026.2]() Tags: [2026-2](), [bug](), [client](), [command-line](), [debug](), [debugger](), [debugging](), [debugging-tools](), [idea](), [intellij](), [intellij-idea](), [java](), [kotlin](), [logpoints]() ### AI overview This walkthrough explains how to use logpoints in IntelliJ IDEA to investigate a bug in a gRPC client-server example that returns incorrect discount values. It covers reproducing the issue, attaching the debugger to the server, and observing program behavior without suspending execution, including improvements in IntelliJ IDEA 2026.2. ### Source excerpt Modern development tools, especially IntelliJ IDEA, have such comprehensive debugging support that for virtually any niche use case, there is a specialized tool for the job. This can make it hard to know where to begin. If you are new to debugging tools and want the biggest return on your learning investment, the best feature [...] ## IntelliJ IDEA 2026.2.3 Is Out! DevFeed: [IntelliJ IDEA 2026.2.3 Is Out!]() Original publisher: [Read original article]() Author: Maria Kosukhina Published: 2026-09-16T10:53:53Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [2026.2](), [Release notes](), [releases](), [Maven](), [Markdown](), [plantuml](), [WSL2](), [Ubuntu]() Tags: [2026-2](), [intellij-idea](), [markdown](), [maven](), [plantuml](), [release-notes](), [ubuntu](), [wsl2]() ### AI overview JetBrains released IntelliJ IDEA 2026.2.3 with fixes and improvements affecting Maven project data, IDE freezes, Markdown preview scrolling, PlantUML support, and applications using WSL2 mirrored networking. ### Source excerpt We've just released IntelliJ IDEA 2026.2.3. You can update to this version from inside the IDE, using the Toolbox App, or using snaps if you are a Ubuntu user. You can also download it from our website. The latest update brings the following improvements: For a comprehensive overview of the fixes, see the release notes. [...] ## Resilient Sync: Your IDE Keeps Helping even when your Build is Broken DevFeed: [Resilient Sync: Your IDE Keeps Helping even when your Build is Broken]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-08-13T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [IntelliJ IDEA](), [ide](), [2026.2](), [configuration]() Tags: [2026-2](), [autocomplete](), [build](), [feature](), [gradle](), [ide](), [intellij-idea](), [kotlin](), [upgrade]() ### AI overview Gradle 9.7 and IntelliJ IDEA 2026.2 introduce resilient sync, allowing the IDE to remain useful when parts of a Gradle build fail to configure. Instead of aborting the entire sync, Gradle provides partial project models, editor data for resolvable Kotlin DSL scripts, and structured failure information. ### Source excerpt You upgrade Gradle, hit sync, and watch every build script turn red. The IDE that was finishing your sentences five minutes ago suddenly has nothing to say, and you're left fixing build logic in what is effectively a very expensive text editor. And the API you need to fix the error is the exact API the IDE can no longer tell you anything about. To get autocomplete back, fix the build. To fix the build, it would help to have autocomplete. Chicken, meet egg. Gradle 9.7, together with IntelliJ IDEA 2026.2, fixes this. The feature is called resilient sync, and it is one of those changes you only notice by its absence once you have it. What goes wrong today Nobody designed the old behavior to be cruel. It falls out of two entirely reasonable decisions that happen to collide. The IDE reasons that if it cannot get a model back from Gradle, it has nothing accurate to show you, so it shows almost nothing. Gradle reasons that if configuration throws, the whole operation failed, so it reports the failure and stops. Both are correct. Together they produce a tool that abandons you precisely when you need it most. The worst version is the multi-project build. You have a hundred subprojects, and one of them (or one shared convention plugin in an included build) has a broken script. In the old world, that single failure takes down the sync for all one hundred. Ninety-nine healthy projects lose their IDE support over one bad line somewhere else in the tree. Power users had a workaround, as charming as workarounds usually are: # The old "please just give me some completion" incantation. Don't rely on this. org.gradle.jvmargs=-Dorg.gradle.kotlin.dsl.provider.mode=classpath It coaxed some completion out of a broken build, frequently broke Gradle's internal state in other ways, and often needed an IDE restart to load new API. Reader, it was not a fix. It was a coping mechanism. What is resilient sync? Resilient sync replaces all-or-nothing with best-effort. When part of your build fails ## How ScyllaDB's Trie-Based Index Delivers Up to 3X More Throughput DevFeed: [How ScyllaDB's Trie-Based Index Delivers Up to 3X More Throughput]() Original publisher: [Read original article]() Author: Tzach Livyatan Published: 2026-06-30T13:03:08Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [benchmarking](), [Benchmark](), [Latency](), [Optimization](), [Caching](), [IO](), [Seastar](), [2026.2](), [Apache Cassandra]() Tags: [2026-2](), [apache](), [architecture](), [benchmark](), [benchmarking](), [cache](), [cassandra](), [deep-dive](), [efficiency](), [engineering](), [latency](), [memory](), [optimization](), [performance](), [product](), [seastar](), [storage](), [time]() ### AI overview ScyllaDB's Trie-based SSTable index replaces separate summary and index files with a prefix tree. The article explains the format change, its storage layout and lookup behavior, and reports benchmark results showing 30% to 230% higher throughput and 31% to 63% lower latency than legacy indexes across four read workloads. ### Source excerpt By transitioning from separate summary and index files to a prefix tree, we optimized cache efficiency, reduced disk I/O, and reduced memory overhead ## ScyllaDB 2026.2: DynamoDB Streams and Vector Search, Trie Indexes, and Strongly Consistent Tables DevFeed: [ScyllaDB 2026.2: DynamoDB Streams and Vector Search, Trie Indexes, and Strongly Consistent Tables]() Original publisher: [Read original article]() Author: Tzach Livyatan Published: 2026-06-29T19:18:20Z Content type: release Language: en Sources: [ScyllaDB]() Topics: [2026.2](), [Alternator (for DynamoDB)](), [API](), [Amazon DynamoDB](), [ScyllaDB Cloud](), [AI search](), [Streams](), [Replication](), [event driven](), [Latency]() Tags: [2026-2](), [amazon-dynamodb](), [api](), [event](), [event-driven](), [features](), [latency](), [performance](), [product](), [replication](), [scylladb](), [scylladb-cloud](), [search](), [streams](), [updates](), [vector]() ### AI overview ScyllaDB 2026.2 adds generally available DynamoDB Streams compatibility and a Vector Search extension to Alternator, alongside ScyllaDB Cloud integrations, Trie index performance improvements, stability updates, and experimental strongly consistent tables and online migration. ### Source excerpt ScyllaDB 2026.2 brings a combination of GA new features, exciting experimental features, and multiple stability and external use case improvements.