span8
span4
FME 2018.1.1.2
这是预期的行为?我已经设置2所列出要由AttributeManager工作台结构中移除。打开在数据检查输出端口的部分结果,他们确实删除。
然而,在第二天变压器(恰好是TopologyBuilder)2个列表上的功能又再次出现时,输出端口在数据检查检查,完全与原来的列表值?不仅如此,但试图与后续AttributeManager,保留指定等将其删除不工作,因为这些变压器不认为无论是在架构已经不复存在的列表,因此将不会出现在可用来修改属性/列表的选择!这些列表继续向下的工作流程中的部分结果,但在架构是不可见的。亚搏在线
此外,如果我有保留指定替代AttributeManager,该列表保持删除(我的猜测是一个解决方法吗?)。我猜这可能是AttributeManager如何试图从名义架构,而不是从实际工作台特征数据实现只删除列表批量功能模式中的错误?(或者在部分结果至少)而保留指定的势力架构拆分来创建数据的一个新的分支?
我认为这个问题是,有列表本身和列表中的属性之间的差异。
该AttributeRemover具有去除列表,并移除属性不同的选项。如果您删除属性的列表,然后在列表依然存在,所以你需要删除的实际清单即可完全摆脱它。我怀疑AttributeManager删除选项只删除属性,不删除列表,因此这个问题。
我想这也取决于列表是如何构建的。我使用“所有属性”添加到列表中建立一个与聚合器。这包括所有FME和fme_color,这不是默认暴露格式等属性。所以,如果我在AttributeManager删除parkList {}。ParkName,那我就还是有parkList {}。fme_color等在该列表中。
但parkList {}。ParkName应该消失。如果你说你删除了(或任何你的属性被称为)在AttributeManager,但它出现在以后的数据,那么我认为这是一个错误。
这是我的工作区(2019.2)的情况下,你想给它一个尝试:ListRemovalMachine.fmwt
希望你会看到同样的结果,因为我做的。
I will say, that I'm not sure it was working for me at first!But I can't recall if it really wasn't working, or I just wasn't looking at the results correctly.I can say definitively that at the time I posted the workspace above, it was working how I'd expect.
Thanks@mark2atsafeand@danatsafe.So it sounds like you don't quite expect what I'm seeing as well.I'll try to get a reasonable sample workspace up that demonstrates what seeing, my production workspace is way too big!
With AttributeManager, you seem to only get an option to remove the List Attributes rather than an option to just select the List and remove it.
However, in my case, I removedallthe List attributes in AttributeManager.Sending these results to Data Inspector, neither the List, nor the Attributes show in the Features which makes it "seems" like it worked.However, on the very next Transformer the entire List, with all of its Attributes, magically reappear in Data Inspector.
Part of its my own inexperience I guess.I'm quickly realising that FME doesn't really "delete" intermediate attributes in all Transformers, even if the user has set them to be "Removed" in AttributeManager.I would hazard a guess that certain Transformer Bulk Modes just clone the data and instead only remove the references to the Attributes rather than remove the Attribute data itself?This would explain why I see the Lists completely disappear after AttributeManager in the Data Inspector results and then reappear as Exposed attributes in the next Transformer's Data Inspector results.
This is important for workspace tuning as the presence of "Hidden", unExposed lists in the data can cause significant performance degradation in downstream Transformers, so for the moment I am using AttributeKeepers to make sure the intermediate Features get split into their own schema without the List(s).It's slower to run than AttributeManager, but it speeds up the downstream Transformers that no longer have to deal with unexposed "hidden" Lists.
@bwn, thanks for sharing the worksapce.I was able to reproduce the symptom with FME 2018.1.2, 2019.1.3.1 and 2019.2.2.
In my quick test, it seems that the AttributeManager won't remove a list attribute if the feature has come from a FeatureJointer.If you replaced the FeatureJointer with a FeatureMerger, the problem would disappear.
I created a simpler workspace that demonstrates the symptom.Can you please take a closer look at this?@mark2atsafe@danatsafe
b18590-attributemanager-not-removing-lists.fmw(FME 2018.1.2)
b19817-attributemanager-not-removing-lists.fmw(FME 2019.2.2)
Thanks@takashi, so I guess that confirms a type of bug!I'll have a look through my production workspace, but yes I would suspect quite a few of the affected AttributeManagers are deriving data from FeatureJoiners output ports.
I hardly ever use FeatureMerger these days as the performance of FeatureJoiner is orders of magnitude faster in performance.Probably the speedier workaround for the moment might be trialling using an extra AttributeRemover pre-processor in the affected Transformer paths.AttributeRemover seems to both work in with a bulk mode and remove the List(s).
I had similarly thought to trial AttributeExposer as a way of "checking" if the Lists were still there but just set to be unexposed, and your sample workspace seems to confirm that.
Thanks for hashing this out.I'll take a look at the workspace to confirm it myself and pass it on to development for a fix.I imagine it's something we'll want to sort out sooner rather than later.
你好@bwn你怎么删除AttributeMana列表吗ger?Were the list attributes actually removed from the features or did they just appear to be removed from under the AttributeManager in your workspace?Please verify with a Logger or by looking at its feature cache.The AttributeKeeper or AttributeRemover are probably better at removing lists.
从列表中动态变化的指标中提取值3个回答
使用编号属性如何重新组织表2个回答
©2020安全亚搏在线软件公司|法律