Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • Y YDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 233
    • Issues 233
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • YottaDBYottaDB
  • DB
  • YDB
  • Issues
  • #191
Closed
Open
Issue created Mar 26, 2018 by K.S. Bhaskar@ksbhaskarOwner

Force access through GNP server even when client and server are on the same host

Final Release Note

GDE CHANGE -SEGMENT -FILE and GDE ADD -SEGMENT -FILE accept a database file name specification of the form @<nodename>:<filepath> where <nodename> is the local host name or a remote host name where the GT.CM GNP server runs. Any database access to such a region/segment by a client process now goes through the GNP server even if <nodename> is the current host. The <nodename>:<filepath> syntax where a database access goes through a GNP server only if <nodename> is not the current host remains supported. The optional @ prefix allows a client to force every database access to go through a GNP server, thereby allowing client processes running different releases of YottaDB to access a database file. [#191 (closed)]

Description

For any database region mapped by the global directory to a server, but for which the server resides on the same machine, YottaDB database logic short-circuits uses in-memory access logic instead of going through the network stack. However, there are situations when it is desirable to force a connection through the network stack, even when client and server are on the same machine, for example if the client and database are for different releases of YottaDB or when the client has signal handling logic that cannot be made compatible with that of YottaDB.

Draft Release Note

GDE CHANGE -SEGMENT -FILE and GDE ADD -SEGMENT -FILE now allow a database file name specification of the form @<nodename>:<filepath> where <nodename> is the local host name or a remote host name where the GT.CM GNP server runs. Any database access to this segment/region by a client process now goes through the GNP server even if <nodename> is a local hostname. Previously it only allowed a remote database file name specification of the form <nodename>:<filepath> where the database access went through a GNP server only if <nodename> was not the local hostname. This syntax continues to be supported. The optional @ prefix allows a client to force every database access to go through a GNP server.

Edited Jul 05, 2020 by Narayanan Iyer
Assignee
Assign to
Time tracking