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
After upgrade all new segments are pre-processed #19153
Comments
Hi @PeteTrombone |
Before the upgrade, the default setting in the segment menu was "SEGMENTED REPORTS ARE PROCESSED IN REAL TIME". An entry in config.ini.php “enable_create_realtime_segments = 1” unfortunately changes nothing. We don't want the default "SEGMENTED REPORTS ARE PRE-PROCESSED". However, it cannot be changed. |
@PeteTrombone do you have browser archiving enabled? |
@sgiehl we have the following settings: |
Ok. Looking at the code that seems clear now:
The option is not pre-selected if browser archiving is disabled. I guess the reason for that is, that pre-processed segments should be preferred if an archiving cron is running. The option to chose a real time segment should still be available, right? What exactly is your problem with having segments preprocessed? |
@sgiehl What exactly is your problem with having segments preprocessed? |
@PeteTrombone So would you need some sort of setting/config to fully disable pre-archived segments, or is it only the pre selection when creating segments that is bothering you? |
@sgiehl yes, we need a setting to fully disable pre-archived segments. |
You can simply skip archiving any segments by appending |
@sgiehl it doesn't seem clear yet what we want, so I'll describe it again.
This is how it was before version 4.3.1 We urgently need a solution here, as archiving takes too long if each segment is pre processed by default. |
Thanks for the detailed description. I guess for now you won't have another possibility than adjusting the code yourself for now, so the default setting is changed. |
Since we upgraded to version 4.3.1 last July, all new segments are pre-processed. We have
no entry “enable_create_realtime_segments = 0” in config.ini.php.
According to the description the default should be processed in real time. But it is not.
An entry “enable_create_realtime_segments = 1” unfortunately changes nothing.
Our current version is 4.9.0
The text was updated successfully, but these errors were encountered: