When processing additional historical data into segments there are two steps: <ol

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Automatically update ts_created & ts_last_edit when invalidating segment reports about matomo HOT 1 CLOSED

9joshua commented on June 21, 2024

Automatically update ts_created & ts_last_edit when invalidating segment reports

from matomo.

Comments (1)

sgiehl commented on June 21, 2024

@9joshua This sound more like a workaround for processing segments beyond the configured time frame.

matomo/config/global.ini.php

Lines 315 to 323 in 826ab46

 ; When archiving segments for the first time, this determines the oldest date that will be archived. 

 ; This option can be used to avoid archiving (for instance) the lastN years for every new segment. 

 ; Valid option values include: "beginning_of_time" (start date of archiving will not be changed) 

 ; "segment_last_edit_time" (start date of archiving will be the earliest last edit date found, 

 ; if none is found, the created date is used) 

 ; "segment_creation_time" (start date of archiving will be the creation date of the segment) 

 ; editLastN where N is an integer (eg "editLast10" to archive for 10 days before the segment last edit date) 

 ; lastN where N is an integer (eg "last10" to archive for 10 days before the segment creation date) 

 process_new_segments_from = "beginning_of_time"

If this is not set to "beginning of time", segments might not be processed for the past by default. Automatically updating the ts_created of a segment would bypass this setting. So we shouldn't do that.

from matomo.

Automatically update ts_created & ts_last_edit when invalidating segment reports about matomo HOT 1 CLOSED

Comments (1)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	; When archiving segments for the first time, this determines the oldest date that will be archived.
	; This option can be used to avoid archiving (for instance) the lastN years for every new segment.
	; Valid option values include: "beginning_of_time" (start date of archiving will not be changed)
	; "segment_last_edit_time" (start date of archiving will be the earliest last edit date found,
	; if none is found, the created date is used)
	; "segment_creation_time" (start date of archiving will be the creation date of the segment)
	; editLastN where N is an integer (eg "editLast10" to archive for 10 days before the segment last edit date)
	; lastN where N is an integer (eg "last10" to archive for 10 days before the segment creation date)
	process_new_segments_from = "beginning_of_time"