span8
span4
span8
span4
理念bytakashi··创造者sqlcreatorpythoncaller亚搏在线变形金刚
喜欢这个想法 - 我有一个复杂的为期3天的过程中,我能减少到1天的过程简单地通过操纵读为了让我能够利用“供应商首先= Yes”或“考生首先=是“在各种变压器。但是我输入的数据往往来自于SQLCreator看着PostGIS的,所以有能力控制这台变压器的读取顺序,以及将提供关于我的一些工作区的显著额外的性能提升。
colinjaconstanccommented·
我已经安装桌面2018.1.2.0,但我没有看到任何运行时的设置,当我右键单击我的创造者。有没有设定我需要改变吗?
我有我的工作区2分标准的创造者:
I have set the one I want to active last to 'Create at End: Yes' but this runs before the data transformation process is complete.
In your case, the first Creator (Create At End: No) runs before any reader and the second Creator (Create At End: Yes) runs after every reader. Even if the workspace didn't contain any readers, the order would be the fixed. You cannot / don't need to control the order of the two Creators, so the "Set Creator Runtime Order" menu command is hidden, I think.
If the two Creators had the same value in the Create At End parameter or you added another Creator to the workspace, the command would be shown.
takashicommented·
Yes, it has been released. Thanks for the great enhancement. However, unfortunately, there are outstanding issues about this functionality. The most critical issue is: there are some creator transformers which always runAfterreaders (e.g. PythonCreator), but they always are listed as "Creators Run之前读者”在造物主运行秩序对话框。我报的不一致在2016.1测试阶段安全支持,但尚未得到解决。希望这将在2017.0版本中得到解决。亚搏在线
fmemeistercommented·
This has been released as part of FME 2016.1 . Visit //www.baooytra.com/downloads to download and try it.
daleatsafecommented·
You voted, we listened. FME 2016.1 betas now have this functionality. I'll paste the comments I made on这种想法的另一个版本下面。请尝试一下,让我们知道您的想法。我还是想对工具提示的执行顺序,让我们知道这将是有益的了。
UPDATE: Originally we used the names of the creators to control their order, but we changed to an explicit dialog to move them up and down. And made it clear that all creators will fire before any features enter a transformer from a reader. And "Create At End" Creators go after the readers have all finished.
Original announcement below:
We are using the lexical order of the names of the transformers to govern the execution. So if you look at them in the navigator pane, that is the order they will fire. They will always go before any features from a "reader" are read in. If you need to interleave that, then you could use a Creator followed by a FeatureReader. We can't technically make Creators go in between "readers" that are otherwise added.
Even if you have custom transformers, within the custom transformer the Creators will fire in the right order, and if you make a custom transformer with no inputs, it will fire in the order of its name with respect to all other Creator-type transformers
我测试了新的功能,“集创建运行秩序”与β-构建16480.这是一个很大的特点。感谢您的增强。
I noticed an inconsistency between the order shown in the "Creator Runtime Order" dialog and the actual order. I reported it to your support team already (C113427). Please check carefully before the official release.
In addition, I think it would be ideal if the user could move any creator transformer (including PythonCreator, SQLCreator, etc.) between "Before Readers" and "After Readers" via the "Creator Runtime Order" dialog. This could be the next step for 2017?
1spatialdavecommented·
对于性能的优化,这将是一流的。能够触发造物主火灾,所有的读者面前,或经过一定的阅读器或所有的读者或者......而这一次后,也许是棘手的,所有的作家都关闭后... ...将是惊人的。它还waould有提供一个可行的替代启动和关机脚本,并在某些情况下,工作空间链接的好处。爱它。
如果你使用FeatureWriters写作——这样做- gather all the Summary features into an Aggregator, when something comes out of that you know all the writing is done...
分享your great idea, or help out by voting for other people's ideas.
© 2020 Safe Software Inc |Legal