Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-3581

Add a system function to return Teiid Server Name

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Major Major
    • 8.12.2, 8.13
    • None
    • Server
    • None

      A user has a 4 node Cluster and would like to get not only the sessionid, vdb and user but the node of the cluster that the user is connected to

            [TEIID-3581] Add a system function to return Teiid Server Name

            The workaround for this is to allow the env function and call env('jboss.node.name').

            With 8.12.2 there will be a node_id system function that will return the jboss.node.name property value. The docs were updated as well.

            Steven Hawkins added a comment - The workaround for this is to allow the env function and call env('jboss.node.name'). With 8.12.2 there will be a node_id system function that will return the jboss.node.name property value. The docs were updated as well.

            As a session property we'll have an issue if we ever move toward replicated sessions. It would be possible to retrieve via object table though. Pushing to 8.12.2 to get out 8.12.1

            Steven Hawkins added a comment - As a session property we'll have an issue if we ever move toward replicated sessions. It would be possible to retrieve via object table though. Pushing to 8.12.2 to get out 8.12.1

            I think we can add as part of the session properties, beyond that it should be up to the user to grab those using the Admin methods etc to get to the Node name IMO

            Ramesh Reddy added a comment - I think we can add as part of the session properties, beyond that it should be up to the user to grab those using the Admin methods etc to get to the Node name IMO

            I don't think I was explicit enough. The main question was whether this seems worth a system function? And if so, then for the embedded case are we saying something like we'll add an EmbeddedConfiguration field for node id or would we expect the system property to be set?

            Steven Hawkins added a comment - I don't think I was explicit enough. The main question was whether this seems worth a system function? And if so, then for the embedded case are we saying something like we'll add an EmbeddedConfiguration field for node id or would we expect the system property to be set?

            Yes, that should be possible, but needs to be handled differently in the embedded case.

            Ramesh Reddy added a comment - Yes, that should be possible, but needs to be handled differently in the embedded case.

            A possible option would be to pull the value from the server property: jboss.node.name

            Van Halbert (Inactive) added a comment - A possible option would be to pull the value from the server property: jboss.node.name

            Assigning to be post 8.12. Ramesh do you have any thoughts here?

            Steven Hawkins added a comment - Assigning to be post 8.12. Ramesh do you have any thoughts here?

            We need to be careful here. Embedded / non-AS depoyments will not have the same notion of node id as AS (which looks like it would just be the jboss.server.name system property). Also since it is straight-forward to use a udf for this, are we sure a system function is needed?

            Steven Hawkins added a comment - We need to be careful here. Embedded / non-AS depoyments will not have the same notion of node id as AS (which looks like it would just be the jboss.server.name system property). Also since it is straight-forward to use a udf for this, are we sure a system function is needed?

              rhn-engineering-shawkins Steven Hawkins
              van.halbert Van Halbert (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: