Repository navigation
fix(query): clear per-connection session state on Bolt LOGOFF - #1844
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 19, 2026
Merged
andrejtonev
marked this pull request as ready for review
October 20, 2026 09:16
andrejtonev
requested review from
Josipmrden,
gitbuda and
vpavicic
as code owners
October 20, 2026 09:16
vpavicic
added a commit
that referenced
this pull request
Oct 21, 2026
* Add Memgraph v3.14.0 and Lab v3.14.0 release note titles Co-authored-by: Cursor <cursoragent@cursor.com> * docs: the bare pattern shorthand takes what a MATCH pattern takes (#1756) * docs: the bare pattern shorthand takes what a MATCH pattern takes The page stated two rules that no longer hold: that the shorthand's pattern cannot introduce names of its own, and that it holds a pattern and nothing else so a filter needs the `MATCH` form. It now takes a variable it declares itself, a trailing `WHERE`, a comma-separated list, a named path and a lone node. The worked example is the filter the old text used to send to the `MATCH` form, written as the shorthand, with output from the page's own dataset. `COLLECT` still has no shorthand. * docs: a pattern holding only a bound variable matches on its value A pattern that names a variable the query has already bound used to be ignored, so the row passed through whatever the variable held. It is now matched: a node is kept, a null matches nothing and drops the row, and a value that is neither raises. This applies to a top-level MATCH and a CALL {} subquery as well as to a subquery expression body, which the pages did not say. Also documents the rule that came with it: a pattern name inside a subquery expression body may not repeat a name from outside the body. Every output block was produced by running the query against its own page's dataset block. * docs: document the nullIf built-in (#1763) * docs(querying): document the nullIf built-in nullIf(value1, value2) answers null where the two arguments are equal and the first argument otherwise, so it takes a value away where coalesce supplies one. * docs(querying): drop nullIf from the unsupported function list It was the only entry under the scalar functions heading, so the heading goes with it. * Add Memgraph v3.14.0 release notes and drop per-release sitemap steps. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: unlisted auth schemes pass through on coordinators without SSO (#1792) Document memgraph/memgraph#4962: on a coordinator, any Bolt scheme not listed in --auth-module-mappings now takes the same passthrough path as basic/none instead of being rejected outright. Describe the two-path rule, the per-scheme denial messages once SSO is configured, and the 3.13 -> 3.14 behavior change. * docs: document disk_available row in SHOW STORAGE INFO (#1791) Documents the new instance-level disk_available row added in memgraph/memgraph#4952. Adds it to the SHOW STORAGE INFO reference table and the example output. Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> * docs: allow UNWIND in an EXISTS, COUNT or COLLECT body (#1783) * docs: add collections.index_of (#1782) * feat: label expressions in node patterns and expressions (#1797) * docs: label expressions in node patterns and expressions * Update pages/querying/differences-in-cypher-implementations.mdx --------- Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> * Document OPTIONAL CALL subqueries (#1776) `OPTIONAL CALL ( scope ) { body }` keeps an input row whose subquery returns no rows, with the subquery's columns set to null - the OPTIONAL MATCH contract. Section 2.4 said the scoped `CALL (...)` form could not be combined with `OPTIONAL` and showed the exact query that now works. It is replaced by 1.7 under the supported uses, and 2.4 now covers the case that is still rejected: `OPTIONAL` on a procedure call rather than on a subquery, with the subquery wrapping that does work. * Complete the Memgraph v3.14.0 changelog. Fill in the remaining breaking, feature, fix, and improvement notes for merged memgraph PRs on this release. Co-authored-by: Cursor <cursoragent@cursor.com> * Add v3.14.0 release notes for nine more PRs and tighten bug-fix skill wording. Co-authored-by: Cursor <cursoragent@cursor.com> * Add v3.14.0 release notes for 18 more milestone PRs. Co-authored-by: Cursor <cursoragent@cursor.com> * feat(dbms): close idle sessions that keep a FORCE-dropped database pinned (#1831) * docs: forced DROP DATABASE closes idle sessions on the dropped database * Apply batched suggestions from code review Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> * Apply batched suggestions from code review Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> --------- Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> * How Memgraph compares and orders values (3.14 comparison series) (#1833) * Document comparisons with null in lists and maps (memgraph#4794) * Document ordering comparisons for values without an order * Fix the ORDER BY sentence: two maps raise an error * Document which values a uniqueness constraint never treats as duplicates * Document ORDER BY and min/max over columns of different types (3.14 comparison series) * Keep only what readers hit; don't restate openCypher's comparison rules * docs: explain and raise the per-process open files limit (#1834) * docs: explain and raise the open files limit (LimitNOFILE, Docker ulimit) * docs: soften open files sizing numbers and document the fs.nr_open ceiling Review follow-up: sizing figures are now approximate, and the section notes that LimitNOFILE cannot exceed fs.nr_open and how to check it. The heading anchor #handle-numerous-open-files-simultaneously is referenced from the Memgraph startup warning. * docs: pin open files limit change to v3.15 and trim unverified sizing numbers * docs: restore upstream heading ids after rebase, add ids to new steps, target v3.14 * docs: open files limit — only the hard limit matters on 3.14; symptoms, warning and INFO line * Document auth queries in explicit transactions (#1836) Auth queries can now run in an explicit transaction and apply together or not at all. Add a section on this to the authentication overview, and update the pages that said auth queries can't run in a transaction. Document that user and tenant profile changes are now refused in explicit transactions. * docs(multi-tenancy): what happens after DROP DATABASE ... FORCE (#1842) * feat(query): tenant DB in SHOW TRANSACTIONS / SHOW ACTIVE USERS + foreign-read UAF fix + precise stuck-drain diagnostics (#1843) * docs: database columns in SHOW ACTIVE USERS INFO and SHOW TRANSACTIONS outputs * docs(server-stats): login timestamp, username and database cells match the 3.14 behaviour * docs: per-session state lasts for the connection; a user switch clears it (#1844) * release notes 3.14: correct #4571 #4573 #4577 #4843 #4932; add #5029 #5129 #5132 #5135 (#1845) * feat(query): SHOW/TERMINATE SESSIONS (#1814) * docs: SHOW SESSIONS and TERMINATE SESSIONS Documents the session management queries from memgraph/memgraph#4577: listing open Bolt sessions and terminating them from another connection, who can see and terminate which sessions, the result columns, and the SESSIONS reserved keyword. Adds both queries to the query privileges table. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: apply review on SHOW/TERMINATE SESSIONS Also fix the TERMINATE TRANSACTIONS parameter claim and add the database column of SHOW TRANSACTIONS. * docs: apply review on session wording and termination behavior * docs: real SHOW TRANSACTIONS output, FORCE note, pooled clients * Apply batched suggestions from code review Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Vlasta <95473291+vpavicic@users.noreply.github.com> Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> * Conditional subqueries with WHEN in CALL, EXISTS, COUNT and COLLECT (#1813) * docs: add conditional CALL subqueries with WHEN * docs: allow WHEN branches in EXISTS, COUNT and COLLECT bodies * docs: drop the predicate evaluation details * docs: use Croatian names in the conditional CALL example * release notes 3.14: add #4524 #4953 #5026 #5032 #5107 #5111 #5126 #5139 #5156 Co-authored-by: Cursor <cursoragent@cursor.com> * update docs for FIPS builds of Memgraph (#1848) * update docs for FIPS builds of Memgraph * update docker page * docs: move WHEN in EXISTS, COUNT and COLLECT bodies to 3.15 memgraph#4985 moved to the 3.15 milestone. * docs: tag non-runnable examples and drop duplicate Previous releases heading * release notes 3.14: #4969 closes only connections whose driver session targeted the database --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Ivan Milinović <44698587+imilinovic@users.noreply.github.com> Co-authored-by: Andi Skrgat <andi8647@gmail.com> Co-authored-by: Katarina Supe <61758502+katarinasupe@users.noreply.github.com> Co-authored-by: andrejtonev <29177572+andrejtonev@users.noreply.github.com> Co-authored-by: colinbarry <colin.barry@memgraph.io> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Dr Matt James <mattkjames7@gmail.com> Co-authored-by: katarinasupe <supe.katarina@gmail.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Documents what happens to per-session state when a pooled Bolt connection switches users:
SET SESSION SETTINGvalues,SET SESSION TRACE, the database selected withUSE DATABASE, andSESSION/NEXTisolation levels last for the client connection and survive a failed query or a rollback (including the BoltRESETa driver sends after a failure); switching to another user on the same connection (the driver re-authenticates withLOGOFF+LOGON) clears them. One short paragraph each inlogs.mdx,monitoring.mdx,multi-tenancy.mdxandtransactions.mdx; no new section (open docs PRs #1814 and #1843 edit the nearby part oftransactions.mdx; this PR merges with both, and with #1831 and #1842, without conflicts).The
SHOW ACTIVE USERS INFOpart of #4932 (login timestampis the most recent login and changes on a user switch,session uuidstays the same) is in #1843, which rewrites that table.Release-note gaps: the 3.14 entry says only that a user switch "clears the previous user's
SET SESSIONsettings". It also clears the session and pending NEXT isolation levels, turnsSET SESSION TRACEoff, resets the selected database, re-applies the requested impersonated user (checking the new user's impersonation privilege), and refreshes the login timestamp. memgraph/memgraph#5135 also fixes the requested-database case on 3.14, so the two entries shouldn't both claim it.Noticed, not fixed:
transactions.mdx: "GLOBAL - apply the new isolation level globally" —SET GLOBALchanges the current database's level.SHOW STORAGE INFOglobal_isolation_levelshows the startup flag, not a runtimeSET GLOBALvalue.query-privileges.mdxlistsSET SESSION TRACEbut notSET SESSION SETTING/RESET SESSION SETTING(no privilege needed either).Checked on the 3.14.0-rc3 package (
8e7e2c28d, contains #4932), Enterprise and Community; user switches made with the Python driver's session-level auth on one pooled connection (same session UUID before and after).Product PR
memgraph/memgraph#4932
Checklist
featureorbugfixlabel added