[
https://issues.apache.org/jira/browse/FLINK-21049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269907#comment-17269907
]
谢波 commented on FLINK-21049:
----------------------------
[~jark]，hello jark，how to build the docs on win10。I get an error when i run
./build_docs.sh -p.
it seems a recusive error.
my env:
ruby 2.6
python 2.7
进入目录“/e/github/MyLanPangzi/master/flink-master/docs/.rubydeps/ruby/2.6.0/gems/libv8-3.16.14.19/vendor/v8/out”
CXX(target)
/e/github/MyLanPangzi/master/flink-master/docs/.rubydeps/ruby/2.6.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/obj.target/preparser_lib/src/allocation.o
../src/allocation.cc:123:3: fatal error: opening dependency file
E:/github/MyLanPangzi/master/flink-master/docs/.rubydeps/ruby/2.6.0/gems/libv8-3.16.14.19/vendor/v8/out/x64.release/.deps/e/github/MyLanPangzi/master/flink-master/docs/.rubydeps/ruby/2.6.0/gems/libv8-3.16.1
4.19/vendor/v8/out/x64.release/obj.target/preparser_lib/src/allocation.o.d.raw:
No such file or directory
123 | } } // namespace v8::internal
| ^
compilation terminated.
An error occurred while installing libv8 (3.16.14.19), and Bundler cannot
continue.
Make sure that `gem install libv8 -v '3.16.14.19' --source
'https://gems.ruby-china.com/'` succeeds before bundling.
In Gemfile:
therubyracer was resolved to 0.12.3, which depends on
libv8
> query_configuration.html content out date
> -----------------------------------------
>
> Key: FLINK-21049
> URL: https://issues.apache.org/jira/browse/FLINK-21049
> Project: Flink
> Issue Type: Bug
> Components: Documentation, Table SQL / API
> Affects Versions: 1.12.1
> Reporter: 谢波
> Priority: Major
>
> [https://ci.apache.org/projects/flink/flink-docs-release-1.12/dev/table/streaming/query_configuration.html]
> code samples is out date.
>
> {{tConfig.setIdleStateRetentionTime(Time.hours(12), Time.hours(24))}}
> {{}}
> Specifies a minimum and a maximum time interval for how long idle state,
> i.e., state which was not updated, will be retained. State will never be
> cleared until it was idle for less than the minimum time and will never be
> kept if it was idle for more than the maximum time.
> When new data arrives for previously cleaned-up state, the new data will be
> handled as if it was the first data. This can result in previous results
> being overwritten.
> Set to 0 (zero) to never clean-up the state.
> NOTE: Cleaning up state requires additional bookkeeping which becomes less
> expensive for larger differences of minTime and maxTime. The difference
> between minTime and maxTime must be at least 5 minutes.
> NOTE: Currently maxTime will be ignored and it will automatically derived
> from minTime as 1.5 x minTime.
> Deprecated
> use setIdleStateRetention(Duration) instead.
> Params:
> minTime – The minimum time interval for which idle state is retained. Set to
> 0 (zero) to never clean-up the state.
> maxTime – The maximum time interval for which idle state is retained. Must be
> at least 5 minutes greater than minTime. Set to 0 (zero) to never clean-up
> the state
> {{}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
