Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add eventIndex and firstEventTimestamp properties to client sessions #517

Closed
mscwilson opened this issue May 27, 2022 · 0 comments
Closed
Assignees
Labels
category:context A new context entity, or changing an existing one, is required. status:completed Completed - but might not be released yet. type:enhancement New features or improvements to existing features.
Milestone

Comments

@mscwilson
Copy link
Contributor

Add the new properties of the 1-0-2 version of the client_session schema.

  • eventIndex – Optional index of the current event in the session. Signifies the order of events in which they were tracked.
  • firstEventTimestamp – Optional date-time timestamp of when the first event in the session was tracked.

These properties are optional to avoid a breaking schema change.

@mscwilson mscwilson added type:enhancement New features or improvements to existing features. category:context A new context entity, or changing an existing one, is required. labels May 27, 2022
@mscwilson mscwilson added this to the 3.2.0 milestone May 27, 2022
mscwilson added a commit that referenced this issue Jun 14, 2022
…close #517)

 PR #521

* Add eventIndex and firstEventTimestamp to sessionState

* Use AtomicInteger for eventIndex

* Move eventIndex to Session class

* Make a copy of the session map

* Remove print statements

* Copy the SessionState again

* Correctly check that datetime timestamp is a string

* Create brand new Tracker in sessionContext test

* Set datetime test to UTC timestamp

* Use expected namespace for EventSendingTests

* Add session eventIndex to copied map
@mscwilson mscwilson added the status:completed Completed - but might not be released yet. label Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:context A new context entity, or changing an existing one, is required. status:completed Completed - but might not be released yet. type:enhancement New features or improvements to existing features.
Projects
None yet
Development

No branches or pull requests

1 participant