As there are some replies already let me just share some observations while configuring the same:
>>>Ingress-Queuing filter is not supported on AE interfaces
[edit interfaces ae1 unit 100 family inet]
'ingress-queuing-filter'
MF Ingress-Queuing_Filter feature supported only on Ethernet interfaces. Failed for interface ae1
error: Failed to read config
commit-check failed
commit-check failed
error: configuration check-out failed
>>>Counting is not supported for Ingress-Queuing-Filter
[edit interfaces xe-2/1/11 unit 0 family inet]
'ingress-queuing-filter'
Unsupported ingress-queuing-filter action 'count' in filter 'test-2'
error: Failed to read config
commit-check failed
commit-check failed
error: configuration check-out failed
# deactivate firewall family inet filter test-2 term 1 then count
# commit
commit complete
>>>In case both are configured as below, below output proves that inet filter over writing the Ingress-Queuing filter
set firewall family inet filter test-1 term 1 then count AF
set firewall family inet filter test-1 term 1 then forwarding-class assured-forwarding
set firewall family inet filter test-1 term 1 then accept
set firewall family inet filter test-2 term 1 then count EF
deactivate firewall family inet filter test-2 term 1 then count
set firewall family inet filter test-2 term 1 then forwarding-class expedited-forwarding
set firewall family inet filter test-2 term 1 then accept
set interfaces xe-2/1/11 unit 0 family inet filter input test-1
set interfaces xe-2/1/11 unit 0 family inet ingress-queuing-filter test-2
set interfaces xe-2/1/11 unit 0 family inet address 160.1.1.2/24
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets : 913 0 pps
Bytes : 115038 0 bps
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets : 1293 9 pps
Bytes : 162918 9600 bps